Carsten Bönsel

Should I use JSR for serious live projects?

The User will find a way to break your App 🧐

Don’t use AI to write your tests

Working in tech as of late:

This is why physics is such a wonderful magic.

Anyone got this to work? It’s not doing anything for me

“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.

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.

📢 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!

@dev_christina Heard good things about contentful.

@dev_christina It depends: Who will ultimately contribute the docs content? If it’s engineers (who are used to markdown / git anyway), then a repo containing markdown will do. Good read otherwise: linkedin.com/pulse/super-us…

"What CMS platform is the best for technical documentation?" Someone in my network has asked a similar question before, who was this...🙋‍♀️your hand or point me to the thread. Please and Thank you!

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?

Spend more time talking about things you like than you do talking about things you don't like.

Damn...

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."

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

@devpato @WeAreDevs @mhevery @dan_abramov @techgirl1908 @FrancescoCiull4 @joel__lord @IObert_ @cassandrafaris Unfortunately, I don't, but living in Berlin. Attending the BeatCTF competition right now... How long are you around?

@Cachsten @WeAreDevs @mhevery @dan_abramov @techgirl1908 @FrancescoCiull4 @joel__lord @IObert_ @cassandrafaris Absolutely!! Are you going to the conf?

On my way to Berlin for @WeAreDevs. I can't wait to meet some familiar faces and meet new ones! @mhevery @dan_abramov @techgirl1908 @FrancescoCiull4 @joel__lord @IObert_ @cassandrafaris Who else will be there?

“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...