Your frontend sends a password to the backend over HTTPS. Should the backend store that password directly in the database?
A. Yes, because HTTPS already encrypted it
B. Yes, if the database is private
C. No, it should be securely hashed before storage
D. No, it should be Base64 encoded instead
It's honestly not worth it for me to use twitter anymore now that I can code from my phone. My usage is way way down. Just replaced one addiction with another addiction
First off, I worked on a portfolio for my startup @kalmitech.(My startup first me get portfolio
Check it out: https://t.co/6iOM5toUpO
Since I'm very much interested in game development. I created a separate website to host all games I create(currently 3)
https://t.co/i96S29tsjj
you claim you become confident in the code when u read it i said ok me too
I use claude to read and verify mine and you have been dragging me since yesterday
so you trust ur judgement
but i shouldn't trust Claude's judgement
you that can't even outcode gemini 1.5 flash lite
I don’t think people realise how big of a deal this is. Alhaji Aliko Dangote is among the 40 richest people in the world. Not top 500 or top 1000. Like only 37 people are ahead of him. Out of billions of people. That is crazy.
In everyday life synchronization means making things happen at the same time.
In a computer it almost always means controlling the order of events.
Most concurrency bugs I've seen come from using the first meaning when the problem is the second.
There’s too much “anyhowness” in the tech space.
Just deploy it anyhow.
Just put it on the server anyhow.
Just use the backend engineer for DevOps anyhow.
Just store the secret anyhow.
Just ship without tests anyhow.
“We’ll fix it when it breaks.”
It works until it doesn’t.
Engineering is not just about making something work.
It is about making it work reliably, securely, maintainably, and intentionally.
And when you’re trying to bring structure into an “anyhow” environment, you quickly realise how difficult it is.
Try working with a well-established European engineering team and you’ll see the difference in standards.
There are processes around how you write code, how you structure PRs, how you commit, how you review, how you deploy and how you document.
You don’t just ship any code because “it works.”
Sometimes your PR can be rejected simply because your commit message doesn’t follow the agreed convention.
At first, it can feel excessive.
But that structure is what makes engineering predictable when the team, codebase and infrastructure grow.