Twenty-eight seconds
Payment provider gives you 28 seconds to answer. Take 29 and it voids, then keeps resending until you reply. We weren't de-duplicating them.
You can guess the rest. (The long version.)
Short posts, the odd thought between longer ones. Newest first, and as a feed: /micro/feed.xml.
Payment provider gives you 28 seconds to answer. Take 29 and it voids, then keeps resending until you reply. We weren't de-duplicating them.
You can guess the rest. (The long version.)
Decided to go all in and bootstrap my first product. Said it on the podcast, so now I have to.
First time I've said my product idea out loud to strangers. Desktop app half written, taught myself C# for it.
Still not sure the pain isn't just mine. (Choosing an audience came later.)
Recorded episode 0.1 of A Bit More Backendy. A podcast for backend devs, because everyone else covers the front end.
The cat, the postman and a creaky chair ruined the first run-through. (Podcasting is hard.)
Interviewing sysadmins. Best line so far: "Legacy servers are like pets, you keep them going for as long as you can."
Best answer on passwords: one key per person per machine, so you can revoke it. The rest of my questions.
ShropGeek (r)evolution in Shrewsbury today. A proper web conference on my doorstep. Pub the night before.
"Isn't it just another time tracker?" No. A tracker tells you what you did so you can bill it. This tells you what you chose to spend your hours on.
Idea for a time tracker where the timer never stops and time is a budget, not a log. Budgets are goals, time spent is spending.
Make the app I want to use.
Turned up to commission heat meters on a building site and only did the click test. Never checked the water flow. Plumbers queued behind me for two days.
Understand what your change touches before you start.
Gave a talk at Skillswap Bristol tonight: A pragmatic look at Symfony, the PHP5 framework. (Did it again at the PHP West Midlands group a few months later.)