Zidan Jaffar
@zidan-jaffar.bsky.social
📤 129
📥 139
📝 1439
Web2 && Web3 Full Stack Dev. | Data Scientist | Cyber Security Analyst ❤
#Football
&
#Movies
pinned post!
WE DON'T BUILD TRUST BY OFFERING HELP... WE BUILD TRUST BY ASKING FOR IT
over 1 year ago
1
1
0
Good engineers reduce bugs. Great engineers reduce the chance of bugs. That’s design, not debugging.
#DevSecOps
#buildinpublic
#100DaysOfCode
about 1 month ago
2
6
1
reposted by
Zidan Jaffar
The Force of Tech
about 1 month ago
True wisdom, this is! Hmmm. Writing code, the easy part it is. To understand the flow, where data moves and where it rests, the Master's path, that is! Clear, your vision must be.
0
2
1
Most engineering problems aren’t about writing code. They’re about understanding: • where data flows • where it stops • where it changes
#DataScience
#buildinpublic
#100DaysOfCode
about 1 month ago
2
7
1
A system feels simple… until something breaks and you have no idea where to start. That’s when design shows.
#DevSecOps
#buildinpublic
#100DaysOfCode
about 1 month ago
0
5
0
Full-stack growth moment: When you stop thinking in files and start thinking in flows. User → request → logic → data → response That’s the real map.
#FullStack
#buildinpublic
#100DaysOfCode
about 1 month ago
1
7
0
Performance isn’t just speed. It’s consistency. Fast sometimes, slow sometimes = unreliable system.
#DevSecOps
#buildinpublic
#100DaysOfCode
about 1 month ago
0
5
1
If it takes too long to understand your own code… imagine what it’s like for someone new to the team. Clarity scales.
#FullStack
#buildinpublic
#100DaysOfCode
about 1 month ago
2
6
0
A good system handles success. A great system handles failure. Design for both.
#DevSecOps
#buildinpublic
#100DaysOfCode
about 1 month ago
2
10
1
Most bugs don’t come from complexity. They come from simple things we assumed were correct.
#FullStack
#buildinpublic
#100DaysOfCode
about 1 month ago
2
6
1
Tweet 5 Full-stack skill isn’t about knowing frontend + backend. It’s about understanding how a single user click turns into: requests → logic → queries → state → cost. That flow is where real engineering happens.
#FullStack
#buildinpublic
#100DaysOfCode
about 2 months ago
0
6
0
The difference between a beginner and an experienced dev: Beginners try to fix the symptom. Experienced devs try to fix the cause.
#FullStack
#buildinpublic
#100DaysOfCode
about 2 months ago
0
4
0
If you can explain your system without opening the codebase, you actually understand it. If you can’t… you understand the syntax, not the system.
#DevSecOps
#buildinpublic
#100DaysOfCode
about 2 months ago
0
5
1
A system doesn’t become complex overnight. It becomes complex one “quick fix” at a time.
#DevSecOps
#buildinpublic
#100DaysOfCode
about 2 months ago
2
7
1
A surprising amount of software engineering is just: • Tracing where data comes from • Understanding why it exists • And figuring out who broke it (usually you)
#FullStack
#buildinpublic
#100DaysOfCode
about 2 months ago
0
12
1
Full-stack engineers don’t just write code. They understand how user behavior becomes system load. Clicks → requests → queries → cost. That pipeline matters.
#FullStack
#buildinpublic
#100DaysOfCode
about 2 months ago
1
8
1
The fastest way to learn software engineering: Build something. Deploy it. Watch it break. Fix it. Repeat. That feedback loop is everything.
#FullStack
#buildinpublic
#100DaysOfCode
about 2 months ago
0
9
1
You can tell how mature a system is by its logs. Good systems explain what’s happening. Bad systems just fail quietly.
#DevSecOps
#buildinpublic
#100DaysOfCode
about 2 months ago
0
4
0
Most performance problems don’t need new tech. They need: • fewer queries • less data • smarter caching • simpler logic Architecture beats optimization.
#DevSecOps
#buildinpublic
#100DaysOfCode
about 2 months ago
3
7
1
The best dev environments remove friction. If it takes 30 minutes to run the project locally, new engineers are already losing momentum.
#FullStack
#buildinpublic
#100DaysOfCode
about 2 months ago
0
5
1
Hidden engineering skill: Knowing when not to add another abstraction layer. Every abstraction has a maintenance cost.
#DevSecOps
#buildinpublic
#100DaysOfCode
about 2 months ago
2
8
0
Fast code is good. Predictable code is better. When systems behave consistently, everything becomes easier to scale.
#DevSecOps
#buildinpublic
#100DaysOfCode
about 2 months ago
0
4
0
A lot of debugging is just asking one question repeatedly: “Where did this value come from?” Follow the data. Always.
#DataScience
#buildinpublic
#100DaysOfCode
about 2 months ago
4
12
1
One sign a system is healthy: You can break one part… and everything else keeps working. Isolation > perfection.
#DevSecOps
#buildinpublic
#100DaysOfCode
about 2 months ago
0
6
2
The best engineers I know don’t panic during outages. They get quiet. They trace. They verify. They isolate. Calm is a technical skill.
#DevSecOps
#buildinpublic
#100DaysOfCode
about 2 months ago
0
5
0
If changing one module forces you to update five others, that’s not growth. That’s coupling.
#DevSecOps
#buildinpublic
#100DaysOfCode
about 2 months ago
1
4
0
Debugging skill isn’t about typing faster. It’s about narrowing the search space faster. That’s experience.
#FullStack
#buildinpublic
#100DaysOfCode
about 2 months ago
2
8
0
Most scalability problems aren’t traffic problems. They’re design decisions that didn’t expect traffic.
#DevOps
#buildinpublic
#100DaysOfCode
2 months ago
0
3
1
A system feels “simple” until you try to explain why it works. Clarity is the real complexity test.
#DataScience
#buildinpublic
#100DaysOfCode
2 months ago
0
6
0
Your codebase tells a story. If it’s hard to follow, future engineers won’t read it — they’ll rewrite it.
#FullStack
#buildinpublic
#100DaysOfCode
2 months ago
0
5
0
Optimization tip: Before tuning performance, ask: “Is this even the bottleneck?” Measure first. Move second.
#FullStack
#buildinpublic
#100DaysOfCode
2 months ago
0
4
1
If your system only works when every service is healthy, you don’t have resilience... you have luck.
#DevSecOps
#buildinpublic
#100DaysOfCode
2 months ago
2
10
1
A surprising amount of “advanced engineering” is just: • Clear naming • Small functions • Fewer assumptions • Good logs Boring scales. Fancy breaks.
#FullStack
#buildinpublic
#100DaysOfCode
2 months ago
0
4
1
Most outages don’t start with explosions. They start with small warnings nobody prioritized. Logs whisper before systems scream.
#DevSecOps
#buildinpublic
#100DaysOfCode
2 months ago
0
3
0
A lot of engineering maturity is realizing: If it’s hard to test, it’s probably hard to maintain.
#DevSecOps
#buildinpublic
#100DaysOfCode
2 months ago
0
5
0
Performance tip: Before rewriting everything in a faster language… check your queries. Check your caching. Check your network calls. Architecture > syntax.
#DevSecOps
#buildinpublic
#100DaysOfCode
3 months ago
1
7
1
You don’t really understand a system until you’ve tried to change one small thing and three unrelated things break. That’s coupling talking.
#FullStack
#buildinpublic
#100DaysOfCode
3 months ago
0
4
1
You can’t optimize what you can’t measure. And you can’t measure what you didn’t design for. Metrics aren’t an afterthought — they’re architecture.
#DataScience
#buildinpublic
#100DaysOfCode
3 months ago
1
4
1
A system without monitoring is just hope in production. Hope is not a scaling strategy.
#DevSecOps
#buildinpublic
#100DaysOfCode
3 months ago
2
8
1
The more I grow as a developer, the more I care about: “How easy is this to undo?” Reversible decisions are underrated.
#FullStack
#buildinpublic
#100DaysOfCode
3 months ago
0
3
0
reposted by
Zidan Jaffar
Kalamazoo Astronomical Society
3 months ago
Mercury was only 50 arcminutes (0.8°) above a very young waxing crescent Moon this evening. KAS member Pete Mumbower captured this image from his home in Vicksburg, MI.
119
6530
931
Frameworks evolve every year. Good engineering habits barely change. Logging. Testing. Clear naming. Defensive design. Boring wins long term.
#FullStack
#buildinpublic
#100DaysOfCode
3 months ago
0
5
0
Most dev growth happens here: • You ship something • It breaks • You trace it end-to-end • You never design that way again Pain is a very efficient teacher.
#DevSecOps
#buildinpublic
#100DaysOfCode
3 months ago
0
5
1
The real reason systems feel “complex” isn’t scale. It’s hidden dependencies. Complexity loves to hide between services.
#DevSecOps
#buildinpublic
#100DaysOfCode
3 months ago
2
5
0
Refactoring rule I live by: If you’re scared to change it, it’s already technical debt.
#FullStack
#buildinpublic
#100DaysOfCode
3 months ago
3
8
1
If you can’t explain your system on a whiteboard without opening your laptop… you probably don’t understand it deeply yet. And that’s fixable.
#FullStack
#buildinpublic
#100DaysOfCode
3 months ago
0
2
1
Frontend devs who understand backend constraints = smoother UX. Backend devs who understand frontend behavior = fewer “why is this slow?” meetings. Systems thinking > titles.
#DevSecOps
#buildinpublic
#100DaysOfCode
4 months ago
0
6
0
Full-stack dev isn’t about knowing everything. It’s about knowing what breaks when you change one thing. That awareness only comes from shipping and debugging real systems.
#FullStack
#buildinpublic
#100DaysOfCode
4 months ago
0
9
1
Security isn’t paranoia. It’s just assuming the internet is creative. 🛡️
#DevSecOps
#buildinpublic
#100DaysOfCode
4 months ago
0
6
0
Data doesn’t lie. But it does mumble, whisper, and occasionally gaslight you. 😅
#DataScience
#buildinpublic
#100DaysOfCode
4 months ago
0
6
0
Full-stack dev is less about knowing everything and more about knowing where to look when things break.
#FullStack
#buildinpublic
#100DaysOfCode
4 months ago
0
5
1
Load more
feeds!
log in