I found a guy who goes around the US asking 70 to 100-year-olds their:
• Biggest Regrets
• Biggest Lessons
• Advice to their younger self
Oddly enough, most of their answers are the same…
Here are my top 8:
How to start your first online business:
(even if you have less than 5k followers)
1. Take the thing you do at work.
2. Build a simple landing page.
3. Write copy that describes that thing.
4. Add a button to "book" a discovery call.
5. Write content about it for 90 days.
6. Answer questions on your content.
7. If people have more, ask them to book.
8. Ask 5 levels of discovery questions:
- What's the problem?
- What have you tried? How did it work?
- What is that costing you?
- How big of a priority is it to fix?
- When are you hoping to have it fixed?
9. Send a recap email about what you learned.
10. Describe how you would fix the problem.
11. Explain how much it will cost.
12. Explain how long it will take.
13. Back into the date they need it fixed by.
14. Ask them if they would like to get started.
15. If they say "no", try again tomorrow.
16. If they say "yes", send them a payment link.
Congrats.
You're running a business.
P.S. Yes, I understand employment agreements and non-competes. Check them both (obviously).
So, let me get this straight. You just got out of college, and you think every system needs to be distributed? That's your big revelation? Let's think about that for a second. Distributed systems are complex, they're expensive, and they're a headache to maintain. You ever heard of KISS? 'Keep It Simple, Stupid.' That's Engineering 101.
You know what happens when you overengineer a solution? You end up with a mess of dependencies, network latency, and a nightmare of debugging. Ever heard of a single point of failure? Now imagine a dozen of them, scattered across different networks.
Oh, so every system needs to be distributed? What about a local bakery's inventory system? You think they need their doughnut count on five different servers Read Lamport's 'Time, Clocks, and the Ordering of Events in a Distributed System', did we? Or perhaps Brewer's CAP Theorem? It's charming, but let's get real. Distributed systems are not a panacea.
First, think about consensus algorithms. Paxos, Raft, Zab - they're not trivial. You've got to manage leader election, log replication, and handle network partitions and failures gracefully. Ever tried debugging a split-brain scenario in a distributed database?
Then there's data consistency. Sure, eventual consistency sounds great in theory, but have you considered the implications for transactional data? Read Eric Brewer's papers on CAP and then tell me about the trade-offs between consistency, availability, and partition tolerance in a high-volume e-commerce application.
Ever heard of a monolith? It's not a dirty word. It's a viable architecture for a vast majority of applications.
Scaling is not just about handling more requests. It's about handling more complexity. So, before you scale out, scale up. Optimize your monolith. Profile your database queries. Cache your responses. These are your bread and butter.
Next you're going to tell me that every application needs to be on the cloud, right? You read Werner Vogels blog and think you need cross-region replication for all your services. That it's cheaper and more scalable? That you can just spin up a kubernetes cluster and scale your application to hundreds of millions of users overnight?
Did you know that Capital One misconfigured an S3 bucket and it led to a massive data breach? Over 100 million customers' data exposed. That's the dark side of cloud computing. Misconfiguration. It's not just about throwing data on the cloud and calling it a day. It's about understanding the nuances of cloud security. Capital One's breach wasn't due to some high-level hacking wizardry; it was a configuration error.
Maybe use your own brain for once.
13 years ago I helped Robert Downey Jr. become Iron Man.
I was nervous but I knew my proven systems would get Robert ripped.
Here are the 7 best exercises I used to build Iron Man that'll help you build muscle:
Students at Carnegie Mellon University have crafted the nimble Iris rover.
It's is setting its sights on moondust close-ups, but by challenging industry norms with limited resources, the project's success could turbocharge independent space research https://t.co/qZbFK0uwpc
I criticized Amazon’s policies in a blogpost.
Now, their lawyers are trying to ruin me.
This is a thread on:
1. What I said about Amazon
2. How Amazon's lawyers have retaliated
3. Why it matters to Amazon customers, sellers, stockholders, and even Amazon itself