I never liked databases as an idea.
You literally send a string query over TCP to postgres and it returns you data over tcp as strings.
There is so much potential to make this whole thing better …. but everyone seems to be just fine with it.
@SumitM_X First squash your own commits to one commit. Then rebase to main. If you really want to preserve all your commits, then I would definitely do merge in most cases, as then you have to resolve conflicts only once.
@unclebobmartin I feel like I make more intermediate commits now with AI-development. If I get something forward enough, I want to make a WIP commit so that AI won't accidentally revert it :D.
@MikaAaltola Oon miettinyt että ne haluis rakentaa sinne varmaan jotain parempaa ohjuspuolustusta, mutta niitä ärsyttäisi tehdä se ilman että ne omistaa sen Grönlannin itse. Niitä kiukuttaa puolustaa EU:ta tai tehdä mitään meidän eteen. Ja tää nyt osuu siihen samaan arpeen.
"Go serverless" they said. "No infrastructure to manage" they said.
Now you have:
- 94 Lambda functions
- Cold start issues you can't fix
- Timeouts you can't control
- Debugging that's a nightmare
- CloudWatch logs that cost $800/month
- Vendor lock-in so deep you can't leave
And your bill?
Higher than running everything on EC2.
Serverless doesn't mean no servers.
It means no control over servers you're paying premium prices for.
I went on a job interview for a Senior SWE role.
They asked me about my experience with Kafka.
I told them how in “Metamorphosis” someone can lose their worth in others’ eyes the moment they stop being useful. It’s a chilling reminder of how fragile our sense of belonging can be when it relies on productivity instead of humanity.
I told them how in “The Trial” he describes the helplessness of confronting institutions that feel arbitrary, unaccountable, and impossible to navigate. The randomness of a giant system can crush your soul. Our brains can’t handle overwhelming inconsistency.
I told them how in “The Castle”, we learn that seeking an approval from an unreachable authority is a trap. If you spend your life chasing validation from humans who don’t care, you’ll end up feeling stuck. The pursuit consumes more than the reward it gives.
I didn’t get the job. The market is tough.
When designing software, should we be reactive, or proactive? Should we adopt YAGNI or Hammock Driven Development as our overarching rule? Should we be 100% “Agile” or 100% waterfall.
Answer: It’s _always_ a mix of moderate amounts of both. The best way to drive a project off the rails is ideologically demand adherence to one side or the other.
Wise teams will spend _some_ time “in the hammock” thinking things through; but not so much that they miss the opportunities to react to the dynamic environment that dominates virtually all software projects.
If you don’t plan, you die.
If you don’t react, you die.