Christian Bürgi

Software engineer and architect in the Java universe, floorball coach (@diving_save), home barista.

[Christian Bürgi @buergich]

"LLMs have the IQ of a toddler with vocabulary that will scare the sh*t out of you" - @mthmulders at #devoxx, explaining why we don't need to be afraid to lose our jobs to AI

[Timon Borter @timon_borter]

Join me at #Devoxx tomorrow for "Practical API Testing with OpenAPI and @citrus_test"! Discover how to detect integration errors early and ship to production with confidence, like we do @PostFinance. Don't miss this Tools-in-Action session. View talk @ https://t.co/sGkIOkfTfE

[Christian Bürgi @buergich]

@khmarbaise Hey, as a follow up from #Devoxx Belgium, how will Maven 4 handle version ranges in the consumer POMs? Would it be a good idea to nail down the version in the published POMs?

[Christian Bürgi @buergich]

Looking to expand our team. It's a challenging and rewarding position while working on the backbone of Switzerland's card payment ecosystem. Millions of customers are relying on our 24/7 services every day!

Feel free to contact for more info.
https://t.co/U7SatNR3E0

[Santiago @svpino]

Software estimates are one of the oldest lies we tell ourselves.

We all know they don't work, but pretend they mean something and later feel enraged when shit hits the fan.

I focused a big part of my undergrad on software estimation.

After graduating, I wrote plenty about the topic.

Then, I started working for a company where I spent years researching how to make better estimates. We sold multiple millions of dollars of software using the tools I built.

I read everything there's to read. I could recite Steve McConnel's "Software Estimation" book from top to bottom.

Here is the most important lesson I learned:

People can't estimate software. It doesn't matter who they are or how much experience they have.

Estimating software reliably is science fiction.

And the best part:

They will ask you to estimate something. They will tell you they understand it's not exact. They will promise they won't hold you accountable.

And then they will. They always do.

There are two solutions for this. Let's start with my recommendations for those who don't have a choice:

1. Remove "quick," "simple," "straightforward," "easy," and every similar word from your dictionary. Never use them. Don't let others use them when referring to your work.

2. Never volunteer an estimate. Everything you say will be used against you.

3. When forced, estimate work you know you can complete today. Always estimate with a range: "It will take me 2 - 4 hours."

4. Estimate anything you won't do today in days and weeks. Say, "I should finish that feature sometime this week." Do not estimate future work in hours.

But we all know your manager will force you to give an estimate. Here is what you should do:

1. Estimate how long you think it will take you to complete the task.

2. Multiply the number by 3. This will be the lower range of your estimate.

3. Double the lower range of the estimate. This will be the upper range.

Example: If you think something will take you 1 day of work, say "between 3 and 6 days."

Here is the funny part:

It won't take you between 3 - 6 days. This is as much bullshit as any other method you can think of.

The true solution for this problem:

Work for a company that doesn't care about estimates.

[Gavin King ⍼⍼⍼ @1ovthafew]

The “deep” problems with the DAO/Repository model are:

- it fails to comprehend the interconnected nature of data
- it insists on a layered architecture where layering is inappropriate
- it falsely claims to abstract over technologies with differences it cannot possibly hide

[Christian Bürgi @buergich]

There is indeed so much wrong with the whole system. Much time & money wasted just because stuff like this ends up as a high-scoring CVE. All on the backs of library maintainers and devs having to deal with false positives.

There are many similar cases like CVE-2022-45868 etc.

[daniel:// stenberg:// @bagder]

CVE-2020-19909 is everything that is wrong with CVEs

Another 9.8 CRITICAL curl problem. All made up.

https://t.co/iiWAnJHCYh

[daniel:// stenberg:// @bagder]

CVE-2020-19909 is everything that is wrong with CVEs

Another 9.8 CRITICAL curl problem. All made up.

https://t.co/iiWAnJHCYh

[Simon Martinelli @simas_ch]

One of the most important things as a software developer is to understand the business. If you don't understand what the users want to do with your software you shouldn't write a single line of code.

[Christian Bürgi @buergich]

@cptblaubaer @khmarbaise Natürlich nicht, da wird selbstverständlich J2SE 1.4 verwendet, Generics sind vom Teufel!!!111

[Christian Bürgi @buergich]

@khmarbaise @the_good_guym @dadideo Usually, when talking about a "DevOps Team" it's more about "a team that handles the DevOps concern for your org" than embracing DevOps practices in your existing structures. It mostly consists of DevOps Evangelists™ and DevOps Engineers™ which is totally the wrong approach IMO

[Shaundai Person @shaundai]

Pro tip: use clickbait commit messages to get your teammates to review your code faster

git commit -m “First she noticed a bug in production. What happens next will SHOCK you!”

[Christian Bürgi @buergich]

This most definitely cuts through the bullshit. Great read (or even better: enjoy the talk)!

[Molly White @molly0xFFF]

Transcript: https://t.co/EBl9C5fes6

[Christian Bürgi @buergich]

@simas_ch @ceki Agreed! There are also other consequences which cam be very serious. At which point, AWS is too big to fail?

Spoiler: I guess it already is...

[Ceki Gülcü @ceki]

AWS generates 20 times more earnings than the rest of Amazon combined. Some may call AWS a successful business model, I would call it outright robbery.

https://t.co/GHrROODlmJ

[Laver Cup @LaverCup]

If there's one thing you watch today, make it this.

#LaverCup | @rogerfederer

[Christian Bürgi @buergich]

@scalajos @mariofusco Guess what happens if your microservices aren't modular..

[Mario Fusco @mariofusco]

On of the duty of a good engineer is using the simplest thing that could possibly work. Whenever possible prefer

- Stateless over Stateful
- Monolith over Microservices
- Local over Remote
- Synchronous over Reactive
- Single-threaded over Parallel
- Declarative over Imperative

[@[email protected] @Nick_Craver]

Build server: "You broke the build."
Me: "THE HELL I DID, GIVE ME THE LOGS TO PROVE MY INNOCENCE!"

Me, reading the logs: