The online whiteboard of Kristofer Palmvik
The Heptagon of Configuration is a term I’m coining to describe a pattern I’ve observed in software configuration, where configuration evolves through specific, increasing levels of flexibility and complexity, before returning the restrictive and simple implementation.
All in all, Copilot has been a great addition to my developer workflow. I would absolutely pay to continue using it in the future. Like any developer tool, it takes some getting used to, but once you’re in the flow, you’ll be coding faster than ever.
If there’s one common issue that all SaaS companies face, it’s isolation. How are customers and their data logically separated from each other? Well, there’s no one answer. And best practices are rapidly changing as companies are becoming more cloud native.
We want bugs to be identified and fixed. Long-running tests can identify those bugs, but a lengthened feedback cycle works against that goal.
By using a checklist, you can increase code quality across the entire organization. Better yet, it serves as an excellent onboarding document to train new reviewers, expanding the pool of reviewers and expediting the review pipeline.
Good luck finding a truly full-stack developer anymore.
Understanding why a fence was put up in the first place is always a good exercise to start with.
The network is reliable Latency is zero Bandwidth is infinite The network is secure Topology doesn’t change There is one administrator Transport cost is zero The network is homogenous
Infrastructure should progressively grow with your workloads and team. How can you choose the right technology now so that you can maximize growth and minimize pain later when you inevitably outgrow it?
A list of notable system prompt leaks from Snap, Bing, ChatGPT, Perplexity AI, and GitHub Copilot Chat.
Every feature has a cost. The obvious costs are time and money. But less obvious costs like screen real estate, brand perception, and organizational scar tissue are often the most costly.
In their quest for product-market fit, most startups should prioritize features that bring them closer to that goal. Dark mode might marginally increase conversion and retention, but it won’t be a stepwise change. Good product managers must allocate resources effectively (even when personally partial to features).
AI-generated code isn’t as good as something you or I could write. It has bugs, often hard to find because we are giving up some of our control. But it’s important to remember: these were the same arguments made in the 1950s through 1970s about compilers vs. assemblers.
A/B tests can be extremely useful in some cases — if you’re at Google or Meta scale or if you’re doing something like performance marketing. But in the vast majority of cases, it’s more pain than it’s worth — and might even be detrimental.