It seems I'm in a minority thinking this is not that great... wind can blow the hat (or the thing from the generalized idea) into traffic, or onto a baby, or any other place to upset people. Also, if the recipient can't/doesn't pick the thing up, then it's littering. From the technical perspective finding heads in a video is not that impressive nowadays... So, I don't get all the excitement...
Wrong, errors should not go unnoticed, let alone helping them to propagate. Cascading effects should be kept on a short leash. System takes one step in the wrong direction, kill it. The two most miserable things are, things not happening and there's no feedback on why, and, the other extreme, when things are overengineered and no one can predict where problems might cascade to.
Get another job first, only then quit this one (then it doesn't matter if u pay them, in the grand scheme of things). Best case you find one. Worst case you don't, then you still have this paying your bills, be happy about it.
Yes. Also, back then in the offline-ish times people shipped working software. Nowadays stuff is huge, slow, craps out all the time, and the risk of stuff breaking with a next update is comparable to the security risks of turning off updates completely.
Everyone used pirated software, Bill still got rich, software developers did make a living, and software prices did not cripple companies. Good old times.
So then don't torture students by making them write long essays and waste their valuable time. Make it the task expressing the argument on a back of a napkin. More thought, less time wasted on writing text-amount. Also less of the teacher's time wasted, do they really read 100x student 3 pages, weekly? Don't they have anything better to do?
So then don't torture students by making them write long essays and waste their valuable time. Make it the task expressing the argument on a back of a napkin. More thought, less time wasted on writing stuff no one ever read properly.
when you program a computer usually there are instant feedback tools like graphic output, debugger, beeps... what I really miss with genetic hacking is this immediate feedback. Did I shake that liquid enough? How degraded was that agent? What is going on in that flask? It would be nice to have a super microscope ad observe, instead of guessing high level what's going on. Well my tomato doesn't glow, how can I debug what went wrong.
Agreed on getting excellent hints from it, shortening the time to figure out stuff. But eg. just now it gave me an example algorithm that, only at 2nd look, turned out to be complete nonsense. You know That colleague, who shines in the eyes of his managers, but peers know that half what he does is garbage.
Exactly. Eg. at some point Ubuntu (true also for Win) decided no proper borders around windows and giant title bars. Now I always struggle findig the border, to grab, between two partially overlapping black terminal windows. And wasting screen realestate on title bars and margins just bugs the hell out of me. I've spent hours trying to fix these things, gave up in the end, there was always something that didn't work right. Why did the world forget doing reasonable defaults that just work without tweaking. Oh and don't get me started on disappearing scrollbars, and lazy loading ui components, which reorder what's under focus/mouse/finger every half a second, and make me do a wrong click if I'm in a hurry
I give ChatGPT a question on how to do X in some programming environment. So far same as googling. But then ok, for me that solution gives errors, or function doesn't exist, 2nd question to ChatGPT, bam half the time it gives something that puts me on the right track. I can't tell google that my python/postgres problem is special, so please do That example, but with such and such restrictions.
managers tend to /want to/ over-simplify things. SWEs have to bear the consequences of every exception to an over-simplified rule, that non-experts did not want to know about. Yeah there's a 1% problem, complex, unrewarding, but we'll spend 90% of the total effort on it because we can't have our system crap out once a month
This is why you never let inexperienced people to come up with standards, patterns, and api-s.
It is impossible to get rid of crap once it is widely adopted.
Caveat: intern doesn't comprehend the problem, goes crazy with decomposition, there's an overengineered mess in the end.
Now there's a 2nd puzzle: how is this mess supposed to solve that task. Which of the thousand-possible call chains, or search constraints, ended up with a particular result.