Ulrich Schmidt-Goertz (@ulrichsg) profile picture

Software developer and resident DDD aficionado @finanzcheck_de

Hamburg, Germany
Joined August 2012
Photo by Ulrich Schmidt-Goertz (@ulrichsg)Photo by Ulrich Schmidt-Goertz (@ulrichsg)Photo by Ulrich Schmidt-Goertz (@ulrichsg)
Ulrich Schmidt-Goertz retweeted
[talking with an English company] > this is our VP of Engineering me: cool, who's the President of Engineering then? *endless silence and confusion*
22
451
32
3,357
Ulrich Schmidt-Goertz retweeted
It was such a pleasure to have @JimmyNilsson at our meetup. Thank you for taking the time to stop by. (And thanks to @andriijas for his spontaneous lightning talk about end-to-end testing, too!)
1
1
5
Ulrich Schmidt-Goertz retweeted
It was a great evening. Thanks again @martinschimak for stopping by to teach us about #storystorming, and thanks @finanzcheck_de for hosting!
5
3
12
Ulrich Schmidt-Goertz retweeted
And on September 12, we’re excited to welcome @JimmyNilsson for his talk on „What really matters“, also at @finanzcheck_de. meetup.com/DDD-HH-Domain-dri…
1
6
Ulrich Schmidt-Goertz retweeted
We’re (almost) back! On September 3, we’ll host @martinschimak who will give a hands-on introduction to „Story Storming“ at the @finanzcheck_de office in Altona. meetup.com/DDD-HH-Domain-dri…
5
2
Ulrich Schmidt-Goertz retweeted
Maybe instead of, "doing agile," we should ask, "where's your feedback loop?" Do you have a feedback loop at all? Is it fast? Is it simple? And does it actually involve end-users?
15
476
36
1,238
Ulrich Schmidt-Goertz retweeted
Things people say when they haven't properly understood the pattern concept: (1) "We're trying to work out if we should use patterns." (2) "Patterns are just missing features in programming languages." (3) "Patterns are for OO/Java/etc. code. We don't use patterns in FP/SQL/etc."
14
36
3
119
Ulrich Schmidt-Goertz retweeted
1/ I've started publishing some Patterns for Decoupling in Distributed Systems on my blog. It's all very rough around the edges for now, I hope to improve them based on feedback.
6
141
15
389
Ulrich Schmidt-Goertz retweeted
Adding logging code for observability often results in low-level code adding cruft to core logic. @ph1 describes a better pattern martinfowler.com/articles/do…
18
289
16
777
Ulrich Schmidt-Goertz retweeted
Ich zahle im Jahr fast 20.000 EUR Steuern an eine Regierung, die mir/uns nun vorwirft, man sei gekauft, weil man von seinem Grundrecht gebrauch macht. Das ist das heftigste, ehrenloseste, undankbarste und absolut abscheulichste, was ich in meinem Leben erlebt habe. #NieMehrCDU
99
2,064
36
13,266
Ulrich Schmidt-Goertz retweeted
Bei der Boeing 737-Max hat mich ja umgehauen, dass MCAS nur an einen der beiden Anstellwinkelsensoren angeschlossen ist. Leute, die so was vorschlagen, planen, bauen oder genehmigen haben nichts in der Luftfahrt zu suchen. Werde kein Mitleid haben, wenn Boeing daran pleite geht.
59
464
162
1,308
Ulrich Schmidt-Goertz retweeted
New RFC for arrow functions / short closures: wiki.php.net/rfc/arrow_funct… Uses fn($x, $y) => $x * $y syntax and implicit by-value binding of variables. The RFC has a detailed discussion on why we're unlikely to get the more popular ($x, $y) => $x * $y syntax...
27
192
46
527
Ulrich Schmidt-Goertz retweeted
Apparently, yes: the state of the art in Node is that you can't tell what triggered a production error. If you only know JavaScript, you should know that other programming languages aren't like this! If you advocate Node, you should tell people this kind of thing up front.
4
21
1
133
Ulrich Schmidt-Goertz retweeted
There's bike infrastructure... & then there's Dutch bike infrastructure. World's 1st suspended bike traffic circle:
404
9,029
426
7,642
For us Mac users, that's Alt + Up Arrow ;)
Another PhpStorm trick I like a lot: use Ctrl + W to select "the next larger thing", e.g. if the cursor is inside a parameter type, it will select the whole type, then the type + name, then all the parameters, then the whole method, etc.
Ulrich Schmidt-Goertz retweeted
Me @Davos. ‘Stop talking about philanthropy, start talking about taxes.’
354
3,794
1,078
7,917
Ulrich Schmidt-Goertz retweeted
Counting negative space gives a language-agnostic approach to code complexity. B is better than A even if we can’t read the code... @AdamTornhill @ddd_eu #dddeurope
1
24
37
Ulrich Schmidt-Goertz retweeted
The world would be a better place if ads targeted on personal information was made entirely illegal. Placing ads based on context and intent is a perfectly fine substitute, and comes with none of the privacy abuse.
The New York Times responded to the GDPR not by geofencing out E.U. readers, but by ending behavioral ad targeting in Europe. As ⁦@Jessdaviesmk⁩ writes, the NYT’s ad revenues there kept increasing anyway. (Via ⁦@jason_kint⁩) digiday.com/media/new-york-t…
18
176
4
491
Ulrich Schmidt-Goertz retweeted
TIL: "for" in programming languages comes originally from the German "für". en.wikipedia.org/wiki/Heinz_…
1
7
19
Ulrich Schmidt-Goertz retweeted
The reality of estimates and schedules for large software projects. I particularly like the ending: feature X was developed by the A team and therefore was supposed to be nearly free for system B. "That proved to be completely wrong."
This quoted post is unavailable.
6
21