Lukas Eder Profile picture
Aug 1, 2022 9 tweets 3 min read Read on X
A brief history of programmers getting mad at computers by DALL·E

It started back in the caves
Same with ancient Romans
During the medieval times
Renaissance, no difference
19th century at the height of impressionism
First 19th century photographic evidence
1950s were no better
Modern day as we know it
And it won't change in the future, either

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Lukas Eder

Lukas Eder Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @lukaseder

Nov 11, 2022
Hey @elonmusk I bet you can’t buy JIRA
Does every one of these tweets go viral now?
Read 4 tweets
Nov 9, 2022
BREAKING: JavaScript has been banned from Twitter for impersonating a real programming language. Image
I don't have a soundcloud, but while you're here, check out jooq.org, the best way to write SQL in JavaScript
Read 5 tweets
Apr 28, 2022
Why is Propagation.REQUIRED the default in Spring? NESTED seems to be a much better default.

A NESTED transactional unit is truly transactional.
A REQUIRED transactional unit can leave data in a weird state, depending on whether it is called top level or from a nested scope.
@simas_ch I really don't see the utility of this behaviour. The only really valid code is to just never catch (and handle) the exception, to always propagate it until it reaches the outer most transactional code.

But then, why even make nested code transactional at all?
@vlad_mihalcea @simas_ch You probably meant ExecutorService and REQUIRES_NEW. That's reasonable in edge cases, but something completely different. In my example, tx2() should see tx1()'s outcome, but not affect it.
Read 14 tweets
Sep 18, 2020
If the Gang of Lukas had written a book about design patterns, the names would be much more catchy.

I'll start:
The Facade pattern would be called the Putting Lipstick On A Pig pattern
The Adapter pattern would be called Darn You Kevin For Not Adhering Implementing My Interfaces pattern
Read 8 tweets
May 28, 2018
1/ There had been a lot of talk about "10x engineers" on Twitter, in the recent past. Some voices went as far as hinting at "10x engineers" being bad for teams / businesses. Those people obviously go way too far. I think the discussion should be much more nuanced. Here's my take
2/ Most people are average by definition. Most people, however, are really good at *something*. And there are some people who are plain simply excellent at *something*. Their excellency may go as far as being 10x as productive as the average. Sounds great! So what's the problem?
3/ Working with someone 10x as good as ourselves can be equally inspiring as it can be frustrating. They're great and make the work they do look much more interesting. Quite possibly, we can learn a lot from them as well. But they're also much much better, and we might never be
Read 13 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(