At what point does technology outpace its usefulness
27.12.2025 14:32
👍 0
🔁 0
💬 0
📌 0
At what point does technology outpace its usefulness
This paradox implies,
essentially, that you have to “solve” the problem once in order to clearly define it and
then solve it again to create a solution that works.
"Horst Rittel and Melvin Webber defined a “wicked” problem as one that could be
clearly defined only by solving it, or by solving part of it (1973).
Came across this definition of software design and it kinda is intriguing
That would suffice
How I hope you guys also streamed the meetup
how was the launch
'Move fast and break things' really meant 'ship broken code, call it MVP, gaslight users into thinking bugs are features'
Silicon Valley turned 'quality control' into a dirty word 💩
Here's free software that runs half the internet'
Corporations: 'Cool, we'll make billions off this and contribute nothing back'
Maintainer: 'I'm burned out and broke'
Everyone: 'Have you tried meditation?' 🙃
The irony of "rush hour" is that the only thing rushing is my patience. It's truly sit and stare at the bumper in front of you hour.
The real skill isn't learning to code - it's learning to Google your errors effectively
Writing code on the weekend to “relax” is wild more like treating burnout with a light sprinkle of… more burnout.
But hey, at least my side project also doesn’t work.
#CodeLife #programming
iOS 18’s liquid glass effect is stunning — especially how it turns white text into a fun little guessing game. Love staring at my screen like it's a magic eye puzzle.
Entity Framework: Because who needs SQL performance when you can write LINQ and pray? #dotnet #EntityFramework #devlife
Background service crashed at 2AM. Logs say "Processing failed" with no item ID, no stack trace, no context. Just vibes.
Now I'm manually scanning 50k database records to find what broke our payment processor.
Reply with your worst "helpful" error message that cost you hours of debugging 👇 #dotnet
.NET Background Services: Because apparently we needed another way to write infinite while loops that crash in production at 3am. Sure, inherit from BackgroundService and pretend your "clean architecture" will handle that unhandled exception better than the Thread.Sleep() #dotnet #legacy
“Why use .NET?”
Because sometimes you want your code to run everywhere, compile strongly, crash rarely, and confuse no one but yourself
Sure, I could debug this LINQ expression… or I could just rewrite it five different ways until one of them compiles
I refactored my app into microservices. Now it fails in separate, distributed, and unpredictable ways. Progress!
It was running in the background and I kept wondering where in the hells were the notification sounds coming from
Beautiful
I woukd love to try that out
Great ,thanks
If you got an article on it,i would love to read it
I've been working a lot with .NET Core and now want to give Blazor a try for a dashboard project..and yes that woukd be helpful
