Loading comment...
Readit NewsDeleted Comment
Loading parent story...
Loading Item...
I can see that future generations are going to think that I'm boomer for preferring the performances of real actors instead of AI slop.
The music industry already went through this with AutoTune and we know how that turned out.
> The music industry already went through this with AutoTune and we know how that turned out.
Yeah, it turned out that almost all mainstream tracks nowadays have post-processing on vocals (the extent varying between genres and styles).
Loading Item...
kfajdsl commented on Claude Code is all you need dwyer.co.za/static/claude... · Posted by u/sixhobbits
Now take Google away, and LSP. And the computer. Write CTEs with a pencil or bust.
I'm exaggerating of ourse, and I hear what you're saying, but I'd rather hire someone who is really really good at squeezing the most out of current day AI (read: not vibe coding slop) than someone who can do the work manually without assistance or fizz buzz on a whiteboard.
For your examples, honestly yeah. A dev should familiar with the basic concepts of their language and tech stack. So yes, they should be able to understand a basic snippet of code without Google, an LSP, or even a computer. They should even be able to "write CTEs with a pencil and paper". I don't expect them to get the syntax perfect, but they should just know the basic tools and concepts enough to have something at least semantically correct. And they certainly should be able to understand the code produced by an AI tool for a take home toy project.
I say this as someone who would definitely be far less productive without Google, LSP, or Claude Code.
Loading parent story...
Loading comment...
kfajdsl commented on Offline.kids – Screen-free activities for kids offline.kids/... · Posted by u/ascorbic
fyi your (?) css is messed up for the 'Show activities by...' images on a viewport that's the size of a macbook pro 14" display split in half vertically
Loading parent story...
Loading comment...
Temporal - if you have strict workflow requirements, want _guarantees_ that things complete, and are willing to take on extra complexity to achieve that. If you're a bank or something, probably a great choice.
Oban - DB-backed worker queue, which processes tasks off-thread. It does not give you the guarantees that Temporal can because it has not abstracted every push/pull into a first-class citizen. While it offers some similar features with workflows, to multiple 9's of reliability you will be hardening that yourself (based on my experience with Celery+Sidekiq)
Based on my heavy experience with both, I'd be happy to have both available to me in a system I'm working on. At my current job we are forced to use Temporal for all background processing, which for small tasks is just a lot of boilerplate.