Christian Bürgi (@buergich) header
Christian Bürgi (@buergich) profile picture

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

Bern, Schweiz
Joined November 2010
Photo by Christian Bürgi (@buergich)Photo by Christian Bürgi (@buergich)Photo by Christian Bürgi (@buergich)Photo by Christian Bürgi (@buergich)Photo by Christian Bürgi (@buergich)Photo by Christian Bürgi (@buergich)Photo by Christian Bürgi (@buergich)Photo by Christian Bürgi (@buergich)Photo by Christian Bürgi (@buergich)Photo by Christian Bürgi (@buergich)
Christian Bürgi retweeted
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 @ devoxx.be/talk?id=19146
2
2
4
81
Christian Bürgi retweeted
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.
501
1,610
234
10,010
1,948,509
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
6
12
33
4,056
Christian Bürgi retweeted
CVE-2020-19909 is everything that is wrong with CVEs Another 9.8 CRITICAL curl problem. All made up. daniel.haxx.se/blog/2023/08/…
32
356
52
1,231
406,347
Christian Bürgi retweeted
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.
23
50
6
268
37,580
Christian Bürgi retweeted
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!”
221
2,100
233
16,113
Christian Bürgi retweeted
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. world.hey.com/dhh/why-we-re-…
4
4
2
9
Christian Bürgi retweeted
If there's one thing you watch today, make it this. #LaverCup | @rogerfederer
3,436
54,003
14,152
258,330
Christian Bürgi retweeted
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
14
74
9
271
Build server: "You broke the build." Me: "THE HELL I DID, GIVE ME THE LOGS TO PROVE MY INNOCENCE!" Me, reading the logs:
7
74
7
706
Christian Bürgi retweeted
Abusing PostgreSQL in the Cloud wiz.io//blog/the-cloud-has-a…
2
32
108
Christian Bürgi retweeted
Don’t call it a comeback: Why @Java is still champ Fantastic article by @rwwmike for @github - featuring commentary from @mmilinkov @EclipseFdn & @karianna @ljcjug - highlighting @adoptium as one of the projects taking Java forward: hubs.ly/Q01jH7C-0
5
1
15
🗣️ "Distill years of Java experience down to a set of best practices that help developers build high-quality Java applications and libraries" Lots of good advice for #Java developers on this site by @JonathanGiles 👍. java.jonathangiles.net/
17
191
11
757
Christian Bürgi retweeted
A typical day of a senior engineer? 👀
294
4,692
673
25,769
Christian Bürgi retweeted
Replying to @buergich
😱
1
1
If you hold a Unix shell up to your ear, you can hear the C.
83
1,150
96
7,472
Christian Bürgi retweeted
Today, after over 5 years of work, HTTP/3 was finally standardized as RFC 9114! rfc-editor.org/rfc/rfc9114.h… Together with RFC 9204 (QPACK header compression) and RFC 9218 (Extensible Priorities) it ushers in an important new chapter for the Web! Proud to have been part of this!
29
1,378
153
4,244
Christian Bürgi retweeted
Duplication is better than the wrong abstraction! https://teapawt.org/t.co/ex60gWrFcl
1
2
1
4
Christian Bürgi retweeted
Heads up: We see a lot of scanning against the #log4j vulnerability and decided to publish a blog post with some guidance: govcert.ch/blog/zero-day-exp… Please patch now!
27
1,129
108
2,256
Christian Bürgi retweeted
Why we DON’T write tickets: - To make managing people possible - To report status, or % complete https://teapawt.org/t.co/ehNdXqOhgJ
2
3