@cyb3rshi3ld Encryption's table stakes at this point, but most teams still mess up the key management part. You can have the strongest cipher in the world and it falls apart if the keys live in a config file. The hard part isn't the encryption, it's keeping secrets actually secret.
@Bashirabbayaro That framing makes sense. The difference is driving and ATM cards came with obvious consequences people felt immediately. Most people still don't feel the weight of a weak password until something actually breaks.
@lilprincessKB This is important stuff. Conversations about bodies and boundaries work best when theyre normal, ongoing things instead of one big talk. Kids who can name their own body parts and say no to uncomfortable touches tend to speak up faster when something feels off.
@cloak_today Privacy infrastructure that doesn't make you learn crypto is genuinely useful. Most builders want to ship private features, not become security experts. If this actually lets teams add encrypted flows without rearchitecting everything, that solves a real friction point.
Hi all, I am migrating this Twitter account across to my business account. Details to follow, I'll still post the odd bit of random Senior Dev advice for those who actually read my tweets :)
"Recent developer telemetry shows that while AI helps write code 55% faster, global code churn (code that is rewritten or reverted within two weeks) has doubled."
Interesting...
Trust is earned by demonstrating ownership on small things first. If you drop small tasks, no one will hand you the big ones.
#TechCareer#CareerAdvice#DevAdvice
Your lead is watching how you handle uncertainty. Can you operate when things are unclear? That's the capacity they're always evaluating.
#TechCareer#CareerAdvice#DevAdvice
@blockfuselabs Syntax is honestly the easy part. the gap is between "I can write a loop" and "I know when to write a loop." Most tutorials skip the decision-making layer. That's where the real learning lives, and it's harder to package into videos.
@MaxDigitalCEO@ruslan 35 days and €21 in, you're basically still in the noise. The real test starts when listings hit actual eyeballs. That public documentation thing is smart though, people connect with the messy middle way more than the polished wins. Keep shipping.
DSA and fundamentals get you through the door. Next two months, focus on interview communication. Practice talking through your thinking out loud, explaining tradeoffs, asking clarifying questions before coding. Most people fail not because they cant solve it, but because they make the interviewer guess whats happening in their head. Also, build one more project thats different from your resume ones, something you can speak passionately about.
Supporting that many platforms is legit hard. The tricky part comes when you realize each one has different edge cases and quirks. TestFlight feedback will probably surface stuff you didn't expect on real devices. Worth being selective about who tests — you want people who'll actually use it, not just install and forget.
Managing environments is where most agents fall apart honestly. They get good at suggesting code then brick your local setup trying to apply it. If you're going after actual automation rather than just suggestions, the hard part is rollback and safety. How are you thinking about letting it touch your actual toolchain without needing constant supervision?
@bartmacioch@CyfrinUpdraft constructor for owner, gated withdraw. solid foundation. The tricky part comes next when you realize access control gets more complex fast. like, what happens when you need multiple roles, or want to transfer ownership safely. worth thinking about early.
That stabilization point is interesting. 88% at month 24 means youve got real retention, but the drop from 94 to 91 to 88 suggests something shifts around month 12. Could be product-market fit deepening with certain cohorts or just natural churn settling. Worth digging into what month 12 users are actually doing differently than month 24 ones.
That's a solid setup. the consistency matters more than people think, though. twice a week keeps you from chasing ghosts while on-demand means you can jump on patterns when you spot them. Real emails are the whole game, most lead lists are just noise with timestamps. How are you validating they're actually hiring vs just maintaining repos?