Make zeroday hard
Day Zero Stack
Access the tech stack driving today’s most ambitious companies, at exclusive discounts.
Snowflake Dev Day | San Francisco | June 4
A day for builders to learn and get hands on with the latest AI and data engineering tools in open source and the Snowflake ecosystem.
The unreasonable effectiveness of just showing up everyday
Six years, no deadlines, and one rule: write some code every day. That slow, stubborn routine turned a side project into a sustainable search company.
I Spent 2 years Launching Tiny Projects | Tiny Projects
Two years ago, frustrated with a long list of unfulfilled project ideas in my phone notes, I decided to give myself one week to try each idea out in its tiniest form.
Making 20% Time Work | begriffs.com
Following Google’s lead many companies have instituted “20% time” for their employees. This is one day per week in which employees can work on projects of their own choosing. The practice keeps developers motivated and sharp, produces tools to solve company problems, and in the best case creates open source which builds prestige and helps recruitment.
Designing for failure
Nobody starts a free-software project hoping that it will fail, so it is a rare project indeed [...]
Quick tips on how to code a cute lazy website from a lazy art hoe with audhd who hates math (no chatbot) - Multi-hyphenate
w/ pictures and gifs by a non-engineer tech person
WRKSHP.tools | User Day
The User Day exercise is a visual tool that promotes a user-centered approach to product and service innovation.
Google.org Impact Challenge: AI for Science
The Google.org Impact Challenge: AI for Science is a $30M global initiative to accelerate scientific breakthroughs that improve human health and build climate resilience.
Why deadlines are pointless and what to do instead
Hot takes and cold truths on software, startups, and the lies we tell ourselves.
Doing nothing at work
Many engineers should be doing less work. I don’t necessarily mean producing less code or fewer changes, but literally working fewer hours in the day. When they do work, they should be working at a slower pace. I like to aim to be running at 80% utilization by default: unless I have a high-pressure project going on, I spend 20% of my workday away from the computer.
