As always with AI - somehow it's your fault - you didn't help it enough - your prompts were inaccurate, your context was too large, the thinking effort was too low, the model was too old, etc. Basically you failed to use your human intelligence to make every effort to enable the AI to do its job better than you ))) It's like pushing a dirtbike up the hill so you can demonstrate how well it climbs.
Given enough motivation (cash) and temporary tools (WD-40 and tape) there is nothing stopping bigtech from doing just that to kill local trade and then 10x prices
Touche, a more or less decent pool robot cleaner is around 3k and doesn't last more than a few years without changing every part but the case itself. Ok I take it - it operates in somewhat "hostile" environment but the point still stands
They chose being controlled and not being Reddit - I can imagine lots of ways to do both - still they chose the toxic way and now they are dead, goal achieved.
thats brilliant - "we gonna take your job away from you, please start using our tools", "we stole the content to sell you, and now we are getting robbed, please feel sorry for us", what's next?
It does actually. I am pro-OSS as sharing knowledge and innovation, I am not sure at this stage I am happy sharing my work with people using LLMs for anything... OSS gonna change for sure.
The power of SQL is not because it is "based on mathematics" - it's because anyone (really, anyone, even with the most basic English skills) could understand it quickly enough to start using it productively with not much technical knowledge. Business analytics, managers of all sorts, manual QA people could grasp the basics in a minute and more complex queries within a few hours. It is very user-friendly and such tools win over anything else. Each time I see an overengineerd/overcomplicated solution that is hard to read/understand - I know it's only "good luck" to the creators.
Not many industries can afford refactoring of the code is not supposed to be changed - additional (unexpected) regression testing costs, risk of downtime, etc. You learn that if it works and is in production - don't touch it.
This is great )) maybe do random templates similar to newspapers (like photo on the left, photo on the right, one block full width, then 3 columns, etc).
You can be right but quite often it helps keeping focus on the forrest rather then getting lost in the trees - at least for me. Boilerplate steals a lot of attention, focus and can just be mentally exhausting.
Similar approach, but I also go a step further with some basic manual architecture/high level contract/stubs setups, just to keep it consistent with other systems (and easier reading as well).
You just learn how to type with your toes. It is an easy skill to master and then comes handy when you drive, or sit at important meetings (you can just keep coding away) and noone's the wiser.