Daniel Glauser

Real life video of working with last week’s top AI model

@ModernTalmud Well played

613

Looking forward to all the AI advancements this year

@psomkar1 It’s just different, both are really useful. I graduated from a highly theoretical CS program with 11 months of experience through paid internships. Both have been extremely valuable. I never would have learned LISP on the job but now I’ve been working with it for over a decade.

Unpopular opinion : Side project teaches you more than any college or degree.

@codewithpri There’s no need to call us out like that.

90% of backend engineers are just people afraid of CSS

@EODHappyCaptain Progress

Two years ago we bought my kid an electric car and spent the night building it Last year we bought him a bike and spent the night building it This year we are buying him LEGOs and he can build them himself.

@DataRepublican @mattvanswol @wickdchiq He’s been on a roll

@mattvanswol @wickdchiq We found our new ratio king.

Psst…mass deportations policy is a form of ethic cleansing

@Milajoy Five minutes, ten if you’re feeling rather generous.

I have been told I am unreasonable about expecting others to be on time SO please actually tell me: Is 25 minutes long enough to wait for someone before I can, in good conscience, leave?

@theo I like GitHub but Gitlab works pretty well too.

It’s probably time for something new to replace GitHub

@iamdevloper Try selling senior leadership on coffee vs. type safety. Marketing 101

why did CoffeeScript fail where TypeScript prevailed?

@SharylAttkisson Just got back from the chiropractor.

Chiropractor. Yes or no? No more information. Just yes or no.

@gunnarmorling You don’t need an ORM if you work with a functional programming language.

"You don't need an ORM" Goes on to build their own custom ORM. Every single time.

@davepl1968 67

Explain this like a 17-year-old.

Thank you for speaking out about this. I went into microservices with an open mind but experienced all the issues you’ve mentioned. When I was speaking out against them eight years ago my words were considered hearsay. I’ll add that none of your customers care about your service topology, if you want to be successful with software development obsess over your customers’ needs and design your architecture to support that.

Microservices is the software industry’s most successful confidence scam. It convinces small teams that they are “thinking big” while systematically destroying their ability to move at all. It flatters ambition by weaponizing insecurity: if you’re not running a constellation of services, are you even a real company? Never mind that this architecture was invented to cope with organizational dysfunction at planetary scale. Now it’s being prescribed to teams that still share a Slack channel and a lunch table. Small teams run on shared context. That is their superpower. Everyone can reason end-to-end. Everyone can change anything. Microservices vaporize that advantage on contact. They replace shared understanding with distributed ignorance. No one owns the whole anymore. Everyone owns a shard. The system becomes something that merely happens to the team, rather than something the team actively understands. This isn’t sophistication. It’s abdication. Then comes the operational farce. Each service demands its own pipeline, secrets, alerts, metrics, dashboards, permissions, backups, and rituals of appeasement. You don’t “deploy” anymore—you synchronize a fleet. One bug now requires a multi-service autopsy. A feature release becomes a coordination exercise across artificial borders you invented for no reason. You didn’t simplify your system. You shattered it and called the debris “architecture.” Microservices also lock incompetence in amber. You are forced to define APIs before you understand your own business. Guesses become contracts. Bad ideas become permanent dependencies. Every early mistake metastasizes through the network. In a monolith, wrong thinking is corrected with a refactor. In microservices, wrong thinking becomes infrastructure. You don’t just regret it—you host it, version it, and monitor it. The claim that monoliths don’t scale is one of the dumbest lies in modern engineering folklore. What doesn’t scale is chaos. What doesn’t scale is process cosplay. What doesn’t scale is pretending you’re Netflix while shipping a glorified CRUD app. Monoliths scale just fine when teams have discipline, tests, and restraint. But restraint isn’t fashionable, and boring doesn’t make conference talks. Microservices for small teams is not a technical mistake—it is a philosophical failure. It announces, loudly, that the team does not trust itself to understand its own system. It replaces accountability with protocol and momentum with middleware. You don’t get “future proofing.” You get permanent drag. And by the time you finally earn the scale that might justify this circus, your speed, your clarity, and your product instincts will already be gone.

@TimSweeneyEpic @rfleury I once worked on a Stratus machine that had to be installed with a modem, if it detected any bad hardware it would call and order a replacement part for its self.

@rfleury An even better idea would be to detect your hardware specs and integrate with Amazon to silently order more DRAM if it detects it's running out of memory.

You know they didn’t write this in a garbage collected language, otherwise the program would delete itself immediately upon install

@shevereshtus I think this is how it should be taught.

I’ve seen tons of variations on fake Talmud quotes before, if that’s the first time I see them present the Gemara as if it’s a book of rhyming limericks. I… don’t know how to react to that.

@debasishg We wouldn’t, we’d do the exact same thing. We review code together, and no matter who wrote it the candidate needs to know how it works and be able to highlight the tradeoffs.

How would you change your interview story if you allow candidates to collaborate with AI of their choice ?

@BeesLittleRanch Never cried but I sure did learn a lot of math. Peak was the paper I wrote for Trigonometry class on Chebyshev polynomials and their usages in analog audio filters.

Seriously though

@The_Kyle_Mann We love a good Shabbos nap after synagogue.

The best sleep you can have in life is a post-church Sunday afternoon nap. Not the best benefit of salvation, but it's up there.

@ennycodes Clojure

Languages that will still be used in 20 years: - C - C++ - JavaScript - Python - Java - Php What am I missing?