IMO, the worst kind of accidental complexity in software is the unnecessary distribution, replication, or restructuring of state, both in space and time.
In other words, legacy code is fine. Legacy data is almost impossible. (Lots of legacy software has legacy data.)
Is Solid (the thing that Tim Berners-Lee keeps talking about) ever actually going to be a thing, or shall I keep ignoring it?
I like the principles but I cannot understand what it *is*.
I love signing into Microsoft Teams so I can click the sign-in button to sign into Microsoft Azure Devops so I can click the sign-in button to sign into Microsoft Azure Devops Pipelines so I can click the
Hey friends, my partner has put together a course to help people with the mental side of landing a tech job. Confidence in interviews, finding stuff that aligns with your values, salary negotiation; that sort of thing.
She’s been a programmer for 15 years and a therapist and coach for a few years now.
She is looking for feedback on the course in exchange for some free coaching on the topic.
If you’re interested, let me know! And boost or forward if you like.
When an LLM outputs, “I panicked”, it does not mean it panicked. It means that based on the preceding sentences, “I panicked” was a likely thing to come next.
It means it’s read a lot of fiction, in which drama is necessary.
It didn’t “panic”. It didn’t *anything*. It wrote a likely sequence of words based on a human request, which it then converted into code that matched those words somewhat. And a human, for some reason, allowed that code to be evaluated without oversight.
