And that's why is hard (and often useless) to try to estimate software efforts.

'If it's your decision, it's design; if not, it's a requirement.' -- Alistair Cockburn

Web backends spoiled me. Single-threaded, serve-n-die mindset makes it really hard to design a long-running service that has many concurrent branches doing work, communicating with each other, competing for resources and expecting failures everywhere. A lot to learn.

Reading Hypermedia Systems (basically a book about HTMX lib). It all just makes sense. hypermedia.systems

Why a subset operator data[from:to] often implemented as [from,to)? Why not [from,to]? Is there an obvious convenience thinking about subsets like that?

I like how PHP emerges with Go through RoadRunner and FrankenPHP. I think it opens up a lot of interesting solutions.

Just having a bunch of passionate developers who prefer to practice their craft in isolation is a very frustrating and expensive endeavour that tends to produce a lot of defects. The biggest issue seems to be the inability to integrate the changes in a timely fashion.

Notes that one writes from time to time to clarify ideas

By testing after coding, we have placed ourselves in a legacy code situation and ensured that testing will be a joyless distraction from “real work.” buff.ly/3HxDDxj

My exploration of "Search in log files" concluded with this program. Use it if you need a lightweight solution to search through log files on your server (or locally). github.com/lezhnev74/heap…

The problem with switch statements and if/else chains is that they replicate like gerbils. If you aren't careful to sequester them in the early stages of your project, you'll find them reproducing in every corner of your application.

I've been waiting for this to be released. Big thank you to Dominik Honnef. #golang gotraceui.dev

Oh, these are golden.

𝗧𝗵𝗲 𝗗𝗼𝗺𝗮𝗶𝗻 𝗹𝗮𝘆𝗲𝗿 𝗳𝗼𝗹𝗱𝗲𝗿 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝘀𝗵𝗼𝘂𝗹𝗱 𝗲𝘅𝗽𝗿𝗲𝘀𝘀 𝗶𝗻𝘁𝗲𝗻𝘁. It took me a few months to understand this concept. The Domain sits at the core of Clean Architecture. It's where you define your entities and the most important business

👨🏻‍🔬 Go memory metrics demystified: - How does process RSS relate to go memory metrics? - How do you identify off-heap allocation problems? - Why does the heap profile under-report memory usage by 2x? If this sounds interesting, check out my new post: datadoghq.com/blog/go-memory…

Shawn Dedalus .·. 🇺🇲 ⚓ The problem is that most customers do not, and can not have a well defined requirements list. Even those who do will be changing that list every week or so. This is the primary constant of software engineering. And the solution is to embrace change and keep your architecture