Readit News__halt_compiler() is fantastic for this (mixing code + data). I've done it a few times.
That's probably true, which is why human most knowledge workers aren't going away any time soon.
That said, I have better luck with a different approach: I use LLM's to learn things that I don't already understand well. This forces me to actively understand and validate the output, rather than consume it passively. With an LLM, I can easily ask questions, drill down, and try different ideas, like I'm working with a tutor. I find this to be much more effective than traditional learning techniques alone (e.g. textbooks, videos, blog posts, etc.).
I became very fond of #TODO ‘s.
If very likely, then you should invest in making the code high-quality. If unlikely, then you should half-ass the code strategically
Always write the simplest thing you can, but no simpler. Finding that line is where all the art is.
I don't think so. Time and time again the client will insist on stuff like "the customer only needs a single email address/phone number" but you're going to pay for that one later if you do the simple thing and add an "email" column.
Same for addresses.
And a whole bunch of other stuff...you need to normalize the heck out of your DB early on, even if you don't need it now. The code you can mostly make a mess of, just choose a good tech stack.
That's a serious amount of non-trivial work to be done in "a few days". The kind of work that should trigger more time consuming activities like security audits, pen tests and the like, before going live, right?
> There's value in having your backtrace surfaced to end users