Search posts, papers, and topics
The author reflects on Sun Microsystems, arguing that despite strong technology, Sun failed because it grew bored with the mechanics of running a business—illustrated by a 2005 startup’s experience where Sun’s sales response was slow and mismatched while Dell’s personal rep closed the deal quickly. The story warns engineers and founders that operational discipline is as critical as technical visi…
Joel Spolsky warns against “architecture astronauts” – people who obsess over high‑level abstractions and buzz‑worthy tech without focusing on real user problems. He argues that engineers should prioritize concrete value over hype.
Mark Seemann reflects on learning to program in the era of LLMs, sharing personal history, doubts about AI‑driven development, and advice to focus on fundamentals and ask verifiable questions of models.
The author argues that mathematics should reward “motivated explanations” – narrative, intuition‑driven expositions that clarify why a theorem is interesting and how it fits into broader context – on par with traditional proof‑oriented work. He defines the concept, contrasts it with proofs, cites examples (Princeton Companion, Thurston’s essays, Chow’s exposition paper), and suggests formalizing…
The author shares personal experiences encouraging conference attendees to approach speakers and give feedback, and urges speakers and organizers to facilitate those conversations. The post is a reminder that a simple compliment or chat can help speakers gauge impact and improve community connections.
The author argues that taking on tasks outside your formal role gives insight and can accelerate delivery, but warns that such “charity” can hide deeper organizational problems like misaligned incentives around buy‑vs‑build and centralization.
A biographical sketch of Jean‑Pierre Serre, covering his early life, education, involvement with Bourbaki, academic positions, and his seminal work on spectral sequences that earned him the Fields Medal.
A speculative opinion piece comparing the rise of AI‑assisted "vibe coding" to the evolution of internet dating, arguing that as AI becomes the default coding partner the term will become obsolete.
A new engineer observes that a big company's reliance on AI for all artifacts (code, specs, tickets) leads to human bottlenecks. Despite AI generating everything, engineers work long hours because nobody understands the output, making the team slow.
Matt Pocock explains how he uses AI agents for software development, emphasizing "strategic programming" and guiding agents with "leading words" from classic engineering texts. He argues that this approach makes engineering fundamentals more critical than ever for creating agent-optimized codebases.
Potts argues AI collapses the university's credentialing signal by cheapening essay and code production, and the author notes that degree devaluation started earlier via grade inflation. He suggests universities double down on human creativity and mentorship to stay relevant.
The post proposes a three‑principle framework—Curiosity, Craft, and Care—to decide how much AI should author each artifact in a software development workflow. It argues that AI can be used aggressively for exploratory, disposable outputs (Curiosity) but should be limited for artifacts that commit the team to decisions (Craft) and for communications that require personal ownership (Care). The auth…
A Zapier survey of 797 U.S. developers finds 63% see more work as non‑technical coworkers use AI coding tools, yet two‑thirds view the shift positively. Developers are moving toward higher‑value strategy, governance, and cross‑functional work, and the top future‑proof skills are security, AI/ML, low‑code QA, strategy, and data engineering.
This presentation explains how marathon incidents expose the gap between work as imagined and work as done, revealing system interdependencies, organizational fragility, and human limits. Effective response requires structured endurance, humane rotations, and holistic cross-functional coordination, offering significant technical and organizational learning.
A personal opinion piece where the author reflects on his over‑enthusiasm for AI tools, describes a recent eye‑opening conversation, and declares he’s stepping back from the AI hype.
Switching the language you think and talk in (e.g., from English to your native Spanish) can reduce mental overhead when debugging complex architectural issues, especially when using LLMs like Codex. The author treats bilingualism as a cognitive tool, not a deficit, and recommends deliberately switching languages—or any mental mode—to break through tough problems.
This article argues that CMMI (Capability Maturity Model Integration) is an outdated and ineffective methodology for software development. It contends that CMMI's focus on institutionalized process devalues individual talent, stifles innovation, and has failed to prove its worth in the broader technology space.
The article argues that starting meetings with everyone’s hand raised and lowering it when finished (counting down) gives facilitators a clear signal of who still needs time, unlike the opposite approach that counts up. Counting down avoids miscounts, reduces failure modes, and leaves a clean hand‑down state for post‑reading discussion.
Practical, low‑level habits for earning client trust on short‑duration consulting gigs – rapid feedback loops, visible work, frequent priority checks, early risk surfacing, and leaving the client self‑sufficient.
The author describes how moving from an in‑house PM role to a consulting one stripped away direct access and authority, forcing a shift toward influence, context‑gathering, and enabling the client team rather than executing decisions herself.
Microsoft renumbered its job levels to start at 40‑70 to add granularity and avoid confusion with the old 1‑14 system; entry engineers now begin at level 59, while lower numbers cover interns and non‑engineering roles.
Addy Osmani warns that AI agents can short‑circuit the hands‑on practice (“reps”) that builds deep expertise and judgment. He recommends deliberately inserting hypothesis‑forming, “why” questioning, diff inspection, failure prediction, and occasional manual coding into the workflow, especially for junior engineers. A 2026 Anthropic study showed junior developers using AI scored 17 % lower on a fo…
Juicebox and Pin are AI‑driven sourcing tools aimed at different buyer personas: Juicebox targets recruiting teams with shared CRM, permissions, and a deep intelligence layer (compensation, growth‑stage, bias audits), while Pin is a solo‑recruiter assistant that automates sourcing, outreach, and scheduling in a single‑user workflow. The article compares scale, collaboration, intelligence, and gov…
Hostinger built an internal 174‑question Mindset Map assessment to surface candidates' and employees' motivations, learning styles, and adaptability. The AI‑processed results are used as one input for hiring and career conversations, not as a decision‑making metric.
This essay argues that AI-assisted development is transforming engineers into full-time reviewers, evaluating AI-generated diffs instead of writing code. This shift introduces new cognitive fatigue and may exacerbate the skill gap between senior and junior engineers.
Reuven Lerner is formally announcing his one-on-one Python coaching sessions, which have been offered informally for years. These sessions cover code review, architecture, Git issues, pair programming, and career advice, providing private, recorded help for $300 per hour.
A SurveyMonkey poll of U.S. adults shows college students mainly make friends in classes, with dorms crucial for on‑campus residents, while Gen Z and Millennials feel less sociable and more lonely than older cohorts. Over half of respondents believe AI usage has degraded face‑to‑face communication skills.
Hostinger will pay up to €2,300 gross per month to Lithuanian staff who volunteer for military service, preserving their jobs and benefits for up to nine months.
Opinion piece arguing that engineers should pursue excellence without needing to justify it, using anecdotes about a fast terminal emulator and a WordPress menu cache to illustrate how over‑engineering can yield unexpected downstream benefits, while also acknowledging the practical need for “good enough” decisions.
CloudBees runs a volunteer program called BeeGiving, giving each employee two paid days a year to volunteer. The article describes a bike‑building activity at the company’s sales kickoff, tying community service to culture and employee engagement.
