God please make today the beginning of great things to come for Arsenal football club, hand us this trophy to kick start our era of dominance. Amen ๐๐ฝโค๏ธ
๐จ๐๏ธ| Thierry Henry: ๐ฃ๏ธ
โYou donโt have to like the way Arsenal F.C. play, but you will respect it, yes, we werenโt great against Bayer 04 Leverkusen, but even on an off night we still found a way to get a draw. Thatโs what top teams do. And at the Emirates, I believe we will finish the job.
I still believe Arsenal will win the Premier League. As for the Champions League, we will see how far this team can go, but let me say it again โ you donโt have to like us.
When Josรฉ Mourinho and Diego Simeone set up their teams the way they want, people call it tactical brilliance. But when Arsenal do things our way, suddenly it becomes a problem.
We are not here to please pundits. We are not here to satisfy rival fans.
We are here to win.โ
Honestly, if you want to secure a backend role in a fintech company that deals heavily with transactions, these are the things you must understand.
If the company actually knows what theyโre doing, their questions will revolve around things like:
Idempotency โ preventing duplicate transactions
Concurrency control โ handling multiple requests safely
Database transactions (ACID)
Distributed systems basics
A lot of people underestimate this side of backend.
But thatโs just the surfaceโฆ
Bookmark and retweet so people can learn from this too
Weโre not wasting 4GB. Most files contain repeated patterns, and compression algorithms store these patterns more efficiently.
For example, instead of writing โAAAAAAAAAAAAโ, ZIP stores โ12Aโ. This reduces the number of bits used for the same data.
Original files are stored raw for fast access, while compression sacrifices CPU power for smaller storage. Compression doesnโt remove data; it removes repetition.
Tech bros in ๐ณ๐ฌ:
Entry Level: โฆ150
Mid Level: โฆ350K โ โฆ500K
Senior Level: โฆ600K โ โฆ800K
Team Lead: โฆ1M โ โฆ1.5M
Techie in ๐ฌ๐ง :
Junior Level: ยฃ1,500
Honestly, this isnโt the life we should be living in this part of the world.
If an API works in Postman but fails in the browser,
first suspect CORS.
Browsers enforce Same-Origin Policy.
Postman doesnโt.
So Iโd:
โข Check browser console
โข Inspect the Network tab
โข Look for failed OPTIONS (preflight) requests
โข Verify CORS headers (Access-Control-Allow-Origin, etc.)
โข Check cookies / auth headers
Most of the timeโฆ
itโs a CORS configuration issue.
AI didnโt replace software engineers.
It exposed who was never one.
If your entire skill is prompting ChatGPT to generate a React UI, youโre not building software o, youโre decorating HTML.
A landing page working on localhost is not a product.
A demo is not a system.
A deployed app is not an engineered architecture.
When scale hits.
When concurrency spikes.
When the database locks.
When production crashes at 4am.
Vibes wonโt save you o.
AI is a tool.
Engineering is depth.
And depth is finally becoming visible again, and na thus part dey sweet me for body.
Vibes coders without engineering knowledge made hacking easier again, created more jobs for engineers...
So e con be like say na HUNTER HUNTED
BYE
So, if you want to avoid a โsanity checkโ from your own codebase, split those responsibilities into different classes and let your controller actually control things like a responsible adult๐.
The scenario above violates the first principle: S, Single Responsibility Principle (SRP).
A class should have one responsibility and one reason to change.
Clean code isnโt about writing more, itโs about separating concerns before they separate your sanity.
Most bugs in large systems donโt come from syntax errors and we all know that. Many come from design decisions, especially TIGHT COUPLING pretending to be โefficiency.โ๐
๐๐ฟ