I use the Twitter web app, and I estimate that only 1 in about 1000, maybe even 1 in 10,000 tweets is “promoted”. Am I just lucky? Or is this a common frequency?
In a few minutes @stilkov takes a look at the @OReillySACon at some of the ways you can determine whether the development efforts you’re undertaking suffer from too much or too little focus on architecture. innoq.com/de/talks/2019/11/g…
Us Germans have very strict criteria when it comes to tax law … or anything else that lends itself to be turned into a ridiculously complex set of rules and processes, TBQH. Kind of a national pastime.
(For the record: Trump, Erdoğan, Orban, Kaczyński, Putin and anyone who supports them can go to hell, too for all I care, but I still consider them to be in a different league)
Call me weird, but I think no one who is able to say no should do any business with any company supporting shitty governments, such as China, Saudi Arabia, North Korea, and any other fucked-up dictatorship
„Höcke ist für mich ein Nazi und die AfD mit ihm auf dem Weg zur NPD 2.0.“ […] „Die AfD ist nicht bürgerlich oder konservativ. Sie ist das Gegenteil. Ihren Führungsleuten fehlen Anstand und Respekt, und sie sucht die Zukunft in der Vergangenheit“
👏👏👏
spiegel.de/politik/deutschla…
RUP was never perceived as waterfall, unless I’m completely misremembering things. It was always incremental/iterative, and everyone doing a five minute read would have told you so
I continue to be be amazed at how a vastly superior architectural pattern – generate HTML on the server, then optionally add to it on the client – became something other than the default choice
To be super clear, I mean "SSR" in the way it's practiced in the JS world today. Specifically "run the JS on the server, ship a snapshot, then ship the JS".
I'm *not* dunking on PHP-era "output HTML, the end". That pattern is *fast*.
"SSR" can be good if we omit the cilent JS