Why you should write MORE shitty code and feel good about it.
With users a product is alive and useful. Without them the product is useless.
If you have ever worked with AWS as a developer then you will know what I mean, AWS tools suck. They suck so bad there is an entire industry focused on solving for this pile of suck.
Wow, your friends and colleagues. These tools make every other command at the command line more powerful.
We all hit bugs that feel impossible to diagnose. The hardest ones to debug are intermittent or inconsistent. How do I fix what works sometimes? Here are some reminders to myself next time I encounter a baffling debugging session.
The majority of the confusion or difficulty I had raising Venture Capital was that I didn’t fully understand the VC business model. I didn’t understand the individual investors and their incentives. I didn’t appreciate the incentives for the fund itself. Nor did I understand what the fund’s investors (Limited Partners aka LPs) were expecting. Hopefully this will help you understand what I didn’t.
Building active-active in multiple regions can be expensive and complex. Serverless-native applications can make it simpler to serve users globally and enable more effective recoveries with less effort.
The gang experiences an AWS outage; customers report SHOWSTOPPERs; the gang triages the issues and attempts to implement an elaborate disaster recovery plan
As a software professional for almost 20 years I've had more passionate discussions about technical debt than any other topic. From all these passionate discussions and online comments I have distilled a taxonomy of the dimensions of debt. What makes a reasoned discussion difficult is that they trade different quantities (mostly unmeasured) of different units across time with different potential probabilities of happening.
I was 16 and about to head off as the youngest member of a month-long wilderness sailing trip. The night before my departure my dad came into my room to check on my packing and inspect my gear. He got serious and gave me the following advice for how to stay alive, keep safe and make the most of my time.
When we use the term technical debt with non-technical business colleagues, they assume, that technical debt is analogous to financial debt. After a few minutes of discussion they are usually relieved to find that there is no actual money problem. How quickly would the CFO get fired if they claimed “we have a lot of debt” but couldn’t produce a balance sheet with lenders, amounts, interest rates and terms?
Going from 0 to 1. How to find the first user for your product.
How to setup an AWS Budget and get notified of forecasted cost overruns using AWS::Budgets::Budget