Two core backend concepts:
Idempotency : Don't perform the same action more than once, even if the same request is repeated.
Deduplication : Don't process or store the same data more than once.
They sound similar, but they solve different problems.
Idempotency protects operations. Deduplication protects data.
This actually makes me sad. Programming is such a fun thing to do in of itself. The completion of the thing task is the ultimate goal, but the road to get there is enjoyable!
Even as i investigate loops and think deeply about how to deploy AI in a real manner that produces real and good code I still make time for 45 minutes to 3 hours a day trad programming.
But regardless of AI being perfect or not, being able to produce quality work or not is not even part of the argument. I just like programming and I think that loving the craft of building the thing itself will ultimately make the thing you are building better. Because you care deeper about it.
Its not about a pretty dress & lipstick you put on it, but the deep thought care you put in to the things no one sees or perhaps its so good they just don't notice. I think that is where the best software is made.
A month ago, I told everyone:
"I've been a backend Engineer for 12+ years. Today, I'm a Principal Engineer at Atlassian.
I've designed systems that handle millions of requests. Sat on both sides of system design interviews.
Reviewed more architecture docs than I can count.
Starting today, I'm breaking down the fundamentals of scaling for the next 25 days.
If you're learning system design bookmark this thread, you're going to get a lot of learning from this."
FYI, the series has concluded. Here are all the concepts, please bookmark, share, learn and the most important build from the learnings you get.
Also, if you have any ideas on what you'd like to see from me, please let me know, any other series or concepts to be broken down.
It's like saying the engineers who builds Plane engines, should build the body, should build the safety features. It's madness. What those companies don't know is the more diversified the engineers who work on a product, the more solid the product is. The same person doing backend and frontend is them making a single engineer though process throughout the application lifecycle.
@grok@UtdGotham It starts with I've been losing sleep, dreaming about the things that we could be. And I think part of the chorus is everything that kills me makes me feel alive. Can you infer?
Look at this one, which world class players? Scholes, Giggs were old, Gary Neville, Wes Brown, Josh O'Shea were average, Rooney was a wonder kid who scored 10-15 goals per season and was more interested in fighting, Ferdinand was coming from a drug ban, Evra and Vidic were unknown. More importantly, that was Chelsea strongest era, Jose Mourinho's Chelsea, Ronaldo came back from the world cup and became a monster. Come off it. To wrestle that title from Chelsea was no ordinary feat, you people were either really young or you were not watching football. Ronaldo won the league for Manchester United in 2006/2007, then we strengthened in 2008 and he went to another level in the UCL after Kaka inspired AC Milan removed us in 2007. Ha. CR7.
Software engineers - the moment is coming when everyone realises it was never about MVPs and toy applications, and that your true value lies in architecture and the quiet backend stuff that makes things work. The revolution is coming. Keep your powder dry. Double down on humans being lazy and not following through. You are the vanguard of the new age.
@Mrbonez_101@Ellis_ You people confuse aesthetics with efficiency. The purpose of football is to win and to win, you have to outscore your opponent, and nobody scored like him consistently during his prime. Read the facts