Learn about the benefits of #TDD, and the way I do it: leveraging "prediction", by playing JitterTed's TDD Game: tdd.cards Soon to be an online game! Buyers of the physical version (below) will get early access to the online version.

Public agencies, consultants, advocacy groups, teachers... they'd all benefit from having a digital library with explainer videos like this one. Any and every transportation topic.

“And I’m thinking that if you design a place where walking and talking to a friend is considered a risky activity, then the problem is not with the person walking and talking. It’s with the kind of environment that you have created.”

RT @TheDonRaab: If you're coding in #Java using lambdas and Java Stream, then this may be the most important blog you read about memory and…

No, everyone is not using AI for everything. gabrielweinberg.com/p/people… People are consuming AI like they eat meat: some are embracing it, some are limiting their use of it, and some are avoiding it altogether.

Early bird registration for @dev2next ends a month from today! Register: dev2next.com/register Join fellow developers and experts to learn about what's next in our field. List of speakers: dev2next.com/speakers Schedule: dev2next.com/schedule

Yesterday, the government published its ‘AI Adoption Plan’ for the creative industries. Somewhat incredibly, it says we should be pushing AI adoption before the government resolves the issues around copyright. This would be great for the AI industry, and terrible for creatives. Important for people to know what the government is pushing here. Short thread on its contents ⬇️ 1/n

Read this now rollingstone.com/music/music…

Many developers underestimate how much better complex code discussions work face to face. Especially when debugging production problems or reviewing architectures. @RichardFichtner reflects on what made #JCON2026 special. Read: javapro.io/2026/06/01/jcon-e… #Java @jcon_conference

The reason why a Danish pension fund banned its investors from buying any SpaceX shares is not just the appalling S-1 filings, where the ONLY profitable segment was Starlink (everything else - the AI, social media, the orbital data centre plans, is burning money at a rate that will bankrupt most companies on this planet). It’s also the governance structure they don’t want to buy into. Elon Musk holds roughly 85% of voting power through a dual-class share structure. He serves as CEO, CTO and chairman of the board, and he cannot be removed as CEO without his own consent. Now, given his personality: - erratic - narcissistic - with self-confessed (and self-evident) ketamine drug addiction - appalling personal life (kids across multiple mothers, and yes - that matters in business) - fringe political views, etc. etc. It is NO surprise that competent investors would not risk the money of their clients. The world is changing and people agreeing to play roulette with their clients’ money are coming to an end. Also, many haven’t forgotten 2008, and yes - the American system (or lack of one, especially guardrails) is still blamed for causing that global recession. Scarcity will lead to investments flowing into more stable, reputable and sustainable ventures.

An AI tax that distributes AI companies’ ill-gotten gains just to the American people is an unfair and dangerous idea. These companies are built on people’s work from all around the world. An AI tax would mean funneling wealth generated by extracting resources from other countries to US citizens. This is digital colonialism. The *real* solution is simply to make AI companies pay for the training data they use. This means the money goes to the people whose work is actually exploited, wherever they are in the world.

Fun fact: When you fire a transaction in a database, you expect isolation and atomicity. But Redis has a minimalist take on transactions. It does not use complex locks or MVCC - it leverages its single-threaded nature to keep things incredibly simple yet highly effective. Today, we dive into how Redis handles transaction queuing, state isolation, and block execution using the sequential nature of event loops. This is the 20th video in the Redis Internals series. In the video, I talk about the mechanics of `MULTI`, `EXEC`, and `DISCARD`, how native database processes maintain connection-specific command queues, and the deliberate design choice of why Redis does not support rolling back a transaction mid-execution. Also, we re-implement this exact transaction engine and array serialization routine from scratch in Go. By the way, 20 videos are now live: 1. Why Single-Threaded Redis Is Fast 2. Writing a TCP Echo Server 3. Wire Protocols 4. Implementing RESP 5. Implementing PING 6. Understanding Event Loops 7. Implementing Event Loops 8. Implementing GET, SET, and TTL 9. Implementing DEL, EXPIRE, and Cleanup 10. Evictions and Implementing first-eviction 11. Implementing Command Pipelining 12. Implementing AOF Persistence 13. Objects, Encodings, and Implementing INCR 14. Implementing INFO and allkeys-random Eviction 15. The Approximated LRU Algorithm 16. Implementing the Approx LRU Algorithm 17. How Redis Caps Its Memory Usage 18. How and Why Redis Overrides Malloc 19. Graceful Shutdown using Signal Handling 20. Redis Transactions Internals Hope this helps you better understand database internals and spark that engineering curiosity. Give it a watch.

Your team will thank you for writing cleaner Java code. 🚀 Master Clean Code, SOLID, Refactoring & Architecture with this Java bundle. 📚 2 Books, $44.98 → $14.99 with this coupon link: leanpub.com/b/javacleancodef… #Java #CleanCode #SoftwareEngineering