Erik Pragt

11.6K posts

Erik Pragt banner
Erik Pragt

Erik Pragt

@epragt

📸 AllScreenshots → https://t.co/oesiV8POGr ✍️ Build In Public → https://t.co/Z3Sf2sW8Jr

Sydney, New South Wales Katılım Temmuz 2009
670 Takip Edilen2K Takipçiler
Erik Pragt
Erik Pragt@epragt·
@mattpocockuk The course seems quite basic for such a premium price. It's unclear what the office hours are (Matts timezone, how do I know what your timezone is?), there's no preview of the video, and the did I mention the price?
English
0
0
4
127
Matt Pocock
Matt Pocock@mattpocockuk·
Folks who looked at my Claude Code cohort and didn't buy it: What stopped you? All feedback is a gift. The more brutal, the better. aihero.dev/cohorts/claude…
English
131
10
227
40.4K
Erik Pragt
Erik Pragt@epragt·
@kgonia7 @RichardFichtner Yes, absolutely. It looks like this nice library, adding a Value annotation here or there, nothing wrong with that. And then suddenly someone starts using Builders all over the place. There's guidelines: "use responsibly", but making a mess is too easy with Lombok.
English
0
0
1
38
Krzysztof Gonia
Krzysztof Gonia@kgonia7·
@epragt @RichardFichtner It's up to project/team decission what's the correct way of buidling objects. Is this lombok issue that tou don't have guidelines?
English
1
0
1
41
💻☕ Richard Fichtner
💻☕ Richard Fichtner@RichardFichtner·
“Lombok is like cocaine. At first, it feels awesome, but after a while, you regret your choices.” I heard that quote at JavaOne last year. It made me laugh back then. Today, during the fireside chat with the Java architects, it came back to me. Brian Goetz, Ron Pressler, John Rose, Alex Buckley, Dan Heidinga, and Paul Sandoz were answering questions directly from the audience. I got the impression that these discussions are not about quick wins. They’re about long-term impact. One Topic was: Java Modules Why aren’t they widely used? The answer was refreshingly honest: Adoption is hard because the surrounding ecosystem isn’t where it needs to be—especially build tools. And that led to the obvious follow-up: Why doesn’t Oracle just ship a build tool with the JDK? The answer, implicitly, was just as interesting: Because their time is better spent on things only they can do. The JDK, the runtime, the language—those are areas where no one else can step in. Build tools? That’s something the community can own. Another Topic was: Streams and performance. There’s often this perception that Streams are “slow.” But the nuance matters: The performance gap shows up in specific edge cases—not in everyday code. And the design choice behind Streams was very intentional: Favor code that developers can read, understand, and maintain. For most applications, that’s the bigger win. What’s interesting is where things might go next. With Project Babylon, there’s a path to optimize these patterns further—without forcing developers to rewrite everything. Write clear code today. Let the platform get smarter underneath you over time. ...And then there’s Lombok. That quote from last year still holds up because it captures a tension many teams feel. Lombok helped fill gaps in the language. But it does so by stepping outside of it. Now that Java itself is evolving—records, pattern matching, and more—the need for those workarounds is shrinking. What stayed with me most today wasn’t a single feature. It was the way these architects think. They’re not optimizing for the next release cycle. They’re thinking in decades. We’re in good hands. #JavaOne
💻☕ Richard Fichtner tweet media
English
8
38
186
16K
Gabor Varadi
Gabor Varadi@Zhuinden·
@kgonia7 @RichardFichtner The only time someone doesn't regret Lombok is when either someone doesn't use Lombok, or they don't just Lombok anymore. As someone who migrated a project off Lombok & replaced most of it with Kotlin, I don't miss Lombok freezing the IDE every few minutes. Just remove Lombok.
English
2
0
2
98
Erik Pragt
Erik Pragt@epragt·
@kgonia7 @RichardFichtner Lombok is probably the worst invention ever, and makes my codebase a living hell. Thanks to Lombok (and the people using it), my classes are now builders, value objects, and much more with no way to know what the correct way of building the object is.
English
1
0
0
41
Krzysztof Gonia
Krzysztof Gonia@kgonia7·
@RichardFichtner I'll bite. Rarely I see someone regretting using Lombok. Devs are using it and nothing really happens. Thanks for the insights! Waiting for the video.
English
2
0
8
563
Erik Pragt
Erik Pragt@epragt·
@Shpigford I've never hosted anything serious myself on Vercel, but I've seen many stories of people getting a bit of traction and a very high bill to go with it, which is why I'm a bit cautious hosting anything on Vercel, and I use CF for most workloads.
English
0
0
1
13
Josh Pigford
Josh Pigford@Shpigford·
@epragt i've never found vercel to be expensive for...anything? 🤷‍♂️ plenty of stuff hosted on both platforms.
English
1
0
0
103
Josh Pigford
Josh Pigford@Shpigford·
vercel will be happy to know i just deployed a site to them after the entire cloudflare pages workflow decided to just stop functioning.
English
7
0
6
5.1K
Erik Pragt
Erik Pragt@epragt·
@headinthebox Absolutely. Saw a few image format wrappers the other day which required Java 22 as a minimum because of the foreign linker api (nightmonkies). Absolutely great development.
English
1
0
1
278
Erik Pragt
Erik Pragt@epragt·
@RichardFichtner I'd like to respond, but the number of emdashes in your post stops me from that :)
English
0
0
3
304
Erik Pragt
Erik Pragt@epragt·
@FoxNews BREAKING: Not "a Tesla". "A car", just like with all your other reports about "cars" which are involved in fires, "cars" which are involved in collisions.
English
0
1
0
18
Fox News
Fox News@FoxNews·
'TERRIFYING': Dashcam video shows the moment a Tesla Cybertruck, allegedly operating in self-driving mode, nearly sent a Houston mom and her infant off a bridge before violently crashing into an overpass barrier. The woman claims she suffered multiple injuries from the incident and is now suing the automaker for $1 million.
English
3.2K
2.2K
14K
6.3M
Erik Meijer
Erik Meijer@headinthebox·
I gotta tell you, folks, Claude Code — very overrated, very brain-dead software. Nobody’s talking about it, but I will. It’s a disaster. You’re typing, you’re focused, beautiful code, really tremendous code — and suddenly, boom — it hijacks you. Total focus theft. You’re thrown into another IntelliJ window like you’ve been kidnapped. Nobody knows how. Nobody understands it. You’re typing, typing, typing — and your characters? Gone. Disappeared. Maybe they’re in another window, maybe they’re in another dimension. Nobody knows. The engineers? They have no idea. Zero clue. This thing just spews output wherever it wants. No respect for the user. No respect for workflow. It’s chaos. Absolute chaos. Very disruptive. Very irritating. Frankly, unacceptable. And they call this intelligent? I don’t think so. I’ve seen smarter autocomplete in Notepad.
English
32
5
182
49.1K
Erik Pragt
Erik Pragt@epragt·
@wholemars Absolutely, we need more public transportation; trains and metros are amazingly fast and cheap transportation for a large part of the commute!
English
0
0
2
49
Whole Mars Catalog
Whole Mars Catalog@wholemars·
today's transportation sucks it costs too much, it's not safe, it pollutes our communities, and it makes us hate our lives we can do much better with today's AI
English
12
21
226
12.1K
Erik Pragt
Erik Pragt@epragt·
@jetbrains I liked the concept of it, but I never understood why changes made by the other person were done on another changeset, and the number of times we broke our builds because of it is non-zero. I would have used it much more if not this.
English
0
0
2
752
JetBrains
JetBrains@jetbrains·
Due to shifting demand, we’re gradually sunsetting Code With Me, our collaborative coding and pair programming service. 2026.1 will be the last IDE release to officially support it, with the service planned to shut down in Q1 2027. Full details: blog.jetbrains.com/platform/2026/…
English
19
20
121
55.4K
Erik Pragt
Erik Pragt@epragt·
Software Developers (1843–2026) Practitioners who translated human intentions into instructions machines could execute. They are survived by the software they wrote, most of which still has at least one known bug.
English
0
1
0
75
Erik Pragt
Erik Pragt@epragt·
Pinsetter boys (1800s–1950s) Children who manually reset bowling pins between frames, replaced by automatic pin-setting machines invented in 1936 and widely deployed by the 1950s.
English
2
0
0
51
Erik Pragt
Erik Pragt@epragt·
Short lived professions over the years: Powder monkeys (1600s–1800s) Lamp lighters (1700s–early 1900s) Pinsetter boys (1800s–1950s) Telegraphers (1840s–1900s) Software Developers (1843-2026)
English
1
0
1
125
Erik Pragt
Erik Pragt@epragt·
Telegraphers (1840s–1900s) Skilled Morse code operators became largely obsolete within about 60 years as the telephone took over.
English
0
0
0
9