project #019: SNOWFALL โ๏ธ๐จ๏ธ
built an interactive snowfall simulator with Python + Pygame โ
โจ different winter themes
๐ต ambient sounds
โ๏ธ animated snowman
19 projects down more to go ๐
watch it here ๐
https://t.co/uEC2JnJjSM
#Python#Pygame#BuildInPublic
been building something called EIDOLON ๐
the goal? 500+ coding projects, one at a time.
hereโs project #018 ๐
https://t.co/hFopqLssbt
just getting started ๐
#Python#BuildInPublic
๐ง Next, I'm working on Linux fundamentals and more interactive cybersecurity challenges.
The goal is to make learning security concepts practical through simulated missions.
๐ป Explore the project on GitHub:
https://t.co/IJNEHNQO8r
#Cybersecurity#Python#BuildInPublic
๐ Updating my Hacker Terminal Game built with Python!
I'm expanding it into a 7-level cybersecurity learning game with terminal & self-hosted web versions ๐ป
๐ Password security
๐ Cryptography
๐ Log analysis
๐งต๐
how to get rich in web3 (without scamming):
learn to find Critical & High Severity vulnerabilities in web3 projects' code
this space's been printing millionaires for years now, easy - all guys who've truly put in the work daily have made it - be the next one๐ซก
Tweet 3/5
I reached out to Perplexity Support and asked if they could either:
โ Change the email linked to my account, or
โ Transfer my chats/data to another account.
Unfortunately, I was told that neither is possible and that I should export each conversation manually.
Tweet 2/5
The problem is that this account contains months of important research, conversations, and work that I rely on daily.
Once my university email is disabled, I'll lose access to everything unless there's a way to migrate or update the account.
Built a terminal-based Hacker Simulation Game in Python to implement my learning till now๐ป
Applying concepts like:
๐ Password cracking
๐ Encryption
๐ Log analysis
๐ Blog: https://t.co/3S460GF5f3
๐ป Code:https://t.co/IJNEHNQO8r
#cybersecurity#python#buildinpublic
Tools/resources you should use daily if you want to succeed as an auditor:
- Cursor
- Claude
- Solodit
- Immunefi writeups
- Hacks post-mortems
All of those will help you but will not do the work for you. You still need to read code every single day.
I just completed Linux Shells room on TryHackMe!
Learn about scripting and the different types of Linux shells. https://t.co/Rw3OwmhUsQ #tryhackme via @tryhackme
Security researcher g_x_w just earned $30,000 for a Medium.
His total earnings are $170k from a critical, a high, and now this medium.
When's he going to get a low to complete the rainbow?
Started Web3 in Jan. Here's the journey till now:
โ 1st grant: $3,000
โ 2nd grant: $10,000
โ Lexicon Hackathon: $15,000
โ Sonic Hackathon: $50,000
โ Landed a mid paying job in web3
โ Got recognition from one of the best people in Solana, @toly.
@solana gave me so much in 2025. Thank you, Solana. Hoping for an even better 2026.
No IIT. No MIT. No fancy job. Just a relentless team and consistent shipping in public. Your turn - whatโs your journey?
Aspiring Rust Engineers โ learn in the right order.
Rust punishes skipping fundamentals more than most languages. Do this in sequence and your life gets much easier.
1. Learn basic programming concepts before Rust Variables, control flow, functions, recursion, basic data structures. Rust is not a first-language-friendly place to discover these.
2. Learn memory & stack/heap concepts before ownership If you donโt understand stack vs heap, lifetimes will feel like black magic instead of common sense.
3. Learn C-style memory models before Rustโs ownership Pointers, references, mutability, aliasing. Rust just makes these rules explicit instead of letting UB happen.
4. Learn borrowing rules before lifetimes syntax Lifetimes are proofs, not magic. The rules come first, the annotations come last.
5. Learn structs & enums before traits Data modeling first. Behavior abstraction later.
6. Learn pattern matching before advanced control flow match is the backbone of idiomatic Rust. Master it early.
7. Learn Result & Option deeply before error frameworks If you donโt understand Result<T, E> propagation, thiserror and anyhow will just hide bugs.
8. Learn ownership-friendly APIs before smart pointers Many problems donโt need Rc, Arc, or RefCell. Avoid them until the compiler forces you.
9. Learn iterators before async Iterators teach you laziness, composition, and ownership flow โ all prerequisites for async Rust.
10. Learn threads & channels before async/await Understand blocking concurrency before non-blocking concurrency.
11. Learn stdlib before crates The standard library is intentionally powerful. Most beginners reach for crates too early.
12. Learn profiling & benchmarking before โoptimizingโ Rust makes fast code possible, not automatic. Measure first.
13. Learn unsafe theory before unsafe code Unsafe is not โadvanced Rust,โ itโs manual enforcement of invariants. Respect it.
14. Learn simple binaries before libraries Binaries teach flow. Libraries teach API design. Donโt reverse it.
15. Learn how the compiler thinks before fighting it Rustโs compiler is strict but honest. If you listen, it teaches you how to write better systems code.
Rust rewards patience.
Rush it, and youโll drown in lifetimes and trait bounds.
Respect the order, and youโll eventually feel like the compiler is working with you, not against you.