Rules for Commenting Code
Unreadable code with comments is inadequate code with comments you cannot trust. Code that is well written rarely needs comments. Only comments that provide additional, necessary information are useful.
The online whiteboard of Kristofer Palmvik
Unreadable code with comments is inadequate code with comments you cannot trust. Code that is well written rarely needs comments. Only comments that provide additional, necessary information are useful.
Suddenly there was no need to pay people like Wilson to write about bat bites and snake nests – AI can do that for free in a few seconds. So what’s a guy to do? “I’m not liking AI but I started to study it every day,” he says. “You have to work with it because it’s not going anywhere and we can’t do anything about it.”
My goal would be to find some data model that could represent the passage of time, the events that occur within it, the geographies associated with those events, and actors that were involved in them. With a solid model behind this, you could visually represent it in different ways, query it around the involvement of various entities, and even overlay different timelines to see where they intersect.
This book offers a comprehensive toolset for organizations to anticipate change, unlock blockers to flow, and maintain competitive advantage in an increasingly uncertain world by connecting the dots between Wardley Mapping, Domain-Driven Design, and Team Topologies.
Let me guess: you've implemented OKRs, but they're not delivering the transformational results you expected. You're not alone. Research shows that 60% of organisations struggle with OKR implementation.
Platform differences make it impossible to hit "true" pixel-perfection, but in practice, this isn't a big deal. We can't guarantee a universal consistency, but we can ensure that each experience is internally consistent, and is faithful to the spirit of the design. That's the most important thing.
Vibe coding creates the appearance of iteration while often denying its substance. Generating new features is trivial, yet the moment feedback demands a fundamental change—a different data model, a shift in architecture, a new user journey—the linearity of the workflow asserts itself. Rewrites become more appealing than true adaptation. This is the essence of velocity without learning. Products evolve through accumulation rather than insight, and technical debt accrues invisibly until it becomes unavoidable.
AI coding solutions are bringing together designers and developers to collaborate in a way they never could before. As one engineering leader recently put it: "Our source of truth needs to be our codebase. If designers can work in a tool they're good at and developers work in a tool they're good at, and they’re both working on the same thing, that's when real collaboration happens. It's a handshake, not a handoff."
Prototyping is the catalyst for product and engineering to truly become one team, and move beyond project handoff. Eliminating handoff and iterating together is more efficient, enjoyable, and user focused… and much less risky.
Past the content and inside the linguistic patterns, you’ll find the creeping uniformity of AI voice. Words like “prowess” and “tapestry,” which are favored by ChatGPT, are creeping into our vocabulary, while words like “bolster,” “unearth,” and “nuance,” words less favored by ChatGPT, have declined in use. Researchers are already documenting shifts in the way we speak and communicate as a result of ChatGPT — and they see this linguistic influence accelerating into something much larger.
5081 links collected between and