Quarkus lead - Distinguished Engineer, Red Hat. Creator of jbang.dev. @maxandersen.xam.dk (bsky)

Joined May 2008
2,074 Photos and videos
Pinned Tweet

I don't believe in deleting content on the internet. You fight ignorance and help education by protecting, not by removing, your voice. As such I've used buff.ly/40SlAMZ to copy ~16.000 tweets from the last 16 years.
4
2,921
Hey @palmin wouldn’t it be cool to add zellij support to @ShellFishApp ? :)
124
Why can kids/teens remove themselves from OpenAI parental controls with just one click of a button? Gawd.
1
199
Collaborative competition is hard. Apple do better.

2
2
3
353
You are not your code. Speaking at Red Hat Developer Day in Aarhus about what happens to developer identity when AI writes the code for you? Not a hype talk. Not a doom talk. An honest one. maxandersen.github.io/presen…

3
12
651
Made it to the main land to attend and present at Red Hat Developer Day at BankData in Aarhus!
10
240
nerdsniped again - tambocam; a webcam viewer for your terminal :) github.com/maxandersen/tambo… Because...why not? :)
1
2
24
2,178
Max Rydahl Andersen retweeted
Replying to @maxandersen
If this is really so important and useful, prove it to me by breaking serialization. No? Oh well, perhaps it wasn’t so critical after all?
2
4
1,204
What are text blocks in a TUI editor called when rendered into 3D ? vtixels ? github.com/tamboui/tamboui/p…
1
2
12
1,259
I present USA the supposedly democratic and free speech country. Imagine any other president ever do anything remotely like this.
1
2
383
Been working on picocli to aesh migration the last few weeks for JBang. The startup difference is amazing - 2-17x faster. JVM mode is now amazing but native mode is even faster lesson learned again and again - reflection is a startup killer; build-time makes all the difference
3
7
24
3,190
Max Rydahl Andersen retweeted
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10 years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored). If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update! I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it. Feeling pretty swell about this mentality with all the supply chain attacks happening.
292
778
8,956
1,184,511
A post about 3D object rendering in a terminal flew by my newsfeed today - couldn't resist and made draft PR for TamboUI github.com/tamboui/tamboui/p…
3
282
Seeing this too. The right balance is probably somewhere in between and depends on maturity and business model of the product running. The ones who find that balance wins. Its definitely going to be an interesting search.
I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out. I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really). It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely. The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture. We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying. I worry.
1
5
836
If you’ve only seen the news about GitLab’s restructuring through social media posts or news sites, it’s worth taking the time to read the actual blog post: about.gitlab.com/blog/gitlab… It’s sad reading in many ways, but it also reflects the reality of the softwa
2
526
TamboUI 0.3 is out in celebration of youtube.com/watch?v=lVwpiSVB… being released :)
TamboUI 0.3 is out! Markdown viewer with streaming, unicode and bracketed paste support, even crispier images and more. See github.com/tamboui/tamboui/r…
1
6
20
1,571
If you are into opensource, performance and just cool technical conversations give Lex Friedmans latest podcast with contributors from ffmpeg and VLC a listen youtube.com/watch?v=nepKKz-M…
1
4
12
1,645
Bring back 2014 when git notes was possible to view on GitHub. github.blog/news-insights/th…
Hear me out…why don’t GitHub and gitlab show git notes ? If they did it seems like a perfect vehicle for agent prompts/memory/plans….
2
480
Hear me out…why don’t GitHub and gitlab show git notes ? If they did it seems like a perfect vehicle for agent prompts/memory/plans….
2
932
Max Rydahl Andersen retweeted
Quarkus Tools for IntelliJ 0.25.0 has been released plugins.jetbrains.com/plugin…! A lot of performance and Qute features improvement and support for Quarkus Roq, Renarde, Web Bundler Here a demo with Quarkus Roq and yaml frontmatter @intellijidea @QuarkusIO
1
5
4
615