
JS engineer, partner TAM @PayPal, previously building applications in @CommerceCloud with @DeptAgency. Here for web development news. He/him/his.
Berlin, Deutschland
Joined October 2013
- Tweets404
- Following340
- Followers67
- Likes2.7K
Carsten Bönsel retweeted
“I don’t have time to exercise” is counter-productive.
Exercise is fuel for motivation and focus. So, exercise improves my per hour output.
My rule: If I say “I don’t have time to exercise”, my life is out of control.
Carsten Bönsel retweeted
GitHub CoPilot saves expensive developer time by purchasing cheap AI time.
So, if a company won't pay for GitHub CoPilot, they either don't realize how much time it saves, or they're bad at math.
Carsten Bönsel retweeted
📢 Join us at the Berlin Developer Meetup!
📅 Date: Tuesday, November 7th
🕒 Time: 3:00 PM - 6:00 PM
📍 Location: Berlin PayPal Meetup Group
(shorturl.at/lpKLY)
Don’t miss this opportunity to connect with us and the community!
Carsten Bönsel retweeted
Bun is exciting.
But Bun’s “all-in-one”approach has many risks and downsides:
🚫 Bun will often lag behind changes to the separate tools it replaces. When JS tools innovate, will Bun be able to quickly support something similar?
🚫 If it’s buggy or insufficient, Bun is harder to replace than separate tools.
🚫 Can I still mix and match tools to select a “best-of-breed” stack?
🚫 Higher risk - The tool chain is reliant on one team instead of many. What if Bun’s small team burns out or runs out of funding? Replacing Bun quickly may be hard.
🚫 Lack of ecosystem. Will cloud providers support Bun? Will a community form around Bun to provide extensions and support? Are the docs sufficient?
🚫 Will Bun honor JS standards or seek to “extend and extinguish”? The latter is a common approach that makes products sticky, but also breaks compatibility. Bun already has some non-standard behaviors.
🚫 Can one small team support something this complex long term?
To be clear, I’m rooting for Bun. But what they’re trying to accomplish is hard and risky. Will it work?
Carsten Bönsel retweeted
Spend more time talking about things you like than you do talking about things you don't like.
Carsten Bönsel retweeted
Some programmers are code-first. They focus on the code.
Other programmers are product-first. They focus on the product and user experience.
Strive to be product-first. Remember the Rule of Good Code:
"If the product doesn’t work well, the code is not good."
Carsten Bönsel retweeted
I’m tired of native apps.
> download this app to register your kid for tennis
> download this other app to see your the tennis schedule
> download this app to pay your bill
> download our app
> download our app!
> download our app!!
Websites are great, btw
Carsten Bönsel retweeted
“I don’t need Tailwind. I’m a CSS expert.”
⚠️Will your docs will be as comprehensive?
⚠️Will your class structure will be as thoughtful?
⚠️Will your dev tools and extensions be as robust?
⚠️Will your build automatically exclude unused styles?
⚠️Will new hires potentially already have experience with your approach?
⚠️Does your entire dev team have a shared understanding of your CSS strategy?
The answer to these questions is almost certainly "No."
So, the most likely outcome of not using Tailwind...is creating an inferior alternative to Tailwind.
It usually doesn't help to just complain. The best thing I learnt while programming is to chop complex problems into pieces. I like to then think about the first thing I can do to start improving. And try to keep doing it every day...
4
34
Carsten Bönsel retweeted
Three misconceptions I’ve noticed among people who don’t “get” Tailwind:
1. People think it’s “inline styles”. (It’s not. It’s utility classes that smart people wrote for you.)
2. People think it’s repetitive/bloated. (It’s not. It’s designed for use with components like React/Vue/etc. Components encapsulate styles and support reuse. And the resulting CSS contains only the Tailwind classes you use.)
3. CSS “experts” think they can do it “better” from scratch. (They can’t. It’ll merely be a poorly documented alternative).
Carsten Bönsel retweeted
there’s a reason everyone in crypto is building infrastructure and barely anyone is building actual apps.
it’s simple to raise millions selling the dream of building the base layer to onboard the the next hundred million users.
it’s much harder to build apps that anyone actually wants to use, so the easy way out is to just build another “x” infra layer **but this time mine is different and better**
Carsten Bönsel retweeted
5. Fucking go for it. Whatever it is. Just try. Maybe you make it. Maybe you don’t. The result isn’t the point.
Your journey, your growth, is the important bit. Don’t let anyone convince you shouldn’t try. Their fear is theirs, it’s not yours to carry.
Carsten Bönsel retweeted
Wen ich gerne mal in einer 🇩🇪 Talkshow sehen würde:
Ein Däne der zeigt wie Ölheizung-Aus seit 2013 geht
Ein Norweger der zeigt wie 80% E-Autos gehen
Ein Niederländer der zeigt wie Tempo 100 geht
Wen ich stattdessen sehe:
Philip Amthor
Christian Dürr
Robin Alexander
Jens Spahn

















