Bard vs ChatGPT: Cual es mejor para PROGRAMAR? 

Sería genial ver un GPT-3.5 vs GPT-4

Genial!

ahi acabo de probar lo de los principios SOLID, y si le pedis por separado te los da, se ve que todavia esta un poco verde, pero tambien entiende bastante

Deberias de hacer la misma comparacion con la nueva version de Google Bard. No solo esta mejorado con mas idiomas disponibles, en mi experiencia personal tiene mejor creatividad al hacer un codigo nuevo y solucionar problemas.

en mi humilde opinion , Para mi tiende a picar codigo mas que nada chat gpt ... ambas, no me creo experto...pero creo que cada tanto necesita feedback y empieza a picar codigo de la forma mas explicita para que puedas corregirlo. no resiste inyeccion de depencia y nose creo que puede servir igual ,pero no es algo que sea el 50% de la fuerza que uno pueda hacerlo de forma humana.

Le hice a Bard la pregunta de los pricipios solidos y a la primera genero esta respuesta (pego solo una, no los otros 2 drafts) - Pegunta: Could you please provide an example of at least 2 solid principles in C#? I need code + explanation View other drafts. Respuesta: - Sure, here are two examples of SOLID principles in C#, with code and explanation: Single Responsibility Principle (SRP) The Single Responsibility Principle (SRP) states that a class should have only one responsibility. This means that a class should only be responsible for one thing, and it should not be responsible for anything else. Here is an example of a class that violates the SRP: C# public class Car { public void Start() { // Start the car engine. } public void Drive() { // Drive the car. } public void Stop() { // Stop the car engine. } } Use code with caution. Learn more This class violates the SRP because it is responsible for three things: starting the car, driving the car, and stopping the car. It would be better to split this class into three separate classes, one for each responsibility. Here is an example of a class that follows the SRP: C# public class CarEngine { public void Start() { // Start the car engine. } public void Stop() { // Stop the car engine. } } public class CarController { public void Drive() { // Drive the car. } } public class Car { private CarEngine engine; private CarController controller; public Car() { engine = new CarEngine(); controller = new CarController(); } public void Start() { engine.Start(); } public void Drive() { controller.Drive(); } public void Stop() { engine.Stop(); } } Use code with caution. Learn more This class follows the SRP because each class is responsible for one thing. The CarEngine class is responsible for starting and stopping the car engine. The CarController class is responsible for driving the car. And the Car class is responsible for assembling the other two classes and providing a way to start, drive, and stop the car. Open/Closed Principle (OCP) The Open/Closed Principle (OCP) states that software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification. This means that software should be designed in such a way that new features can be added without having to change existing code. Here is an example of a class that violates the OCP: C# public class Car { public void Drive() { // Drive the car. } } Use code with caution. Learn more This class violates the OCP because it is not open for extension. If we want to add a new feature to the car, such as the ability to drive in reverse, we will have to modify the Car class. Here is an example of a class that follows the OCP: C# public abstract class Car { public abstract void Drive(); } public class Sedan : Car { public override void Drive() { // Drive the sedan. } } public class Truck : Car { public override void Drive() { // Drive the truck. } } Use code with caution. Learn more This class follows the OCP because it is open for extension. We can add new types of cars by creating new classes that inherit from the Car class. This way, we can add new features to the cars without having to modify the Car class. These are just two examples of SOLID principles in C#. There are many other principles that can be applied to object-oriented programming. By following these principles, you can write better, more maintainable code. Sources github.com/psahni/TAA www.linkedin.com/pulse/solid-principles-c-ottorino-bruni www.quabr.com/65942370/open-closed-pri

Que pasa con la privacidad del código que compartimos con CHATGPT y BARD?

Por los ejemplos, Bard todavía no sirve de mucho salvo que dicen que tiene la data actualizada.