Captain retweeted
Cycle 3 is officially closed with 89 Mini Apps submitted! 🎉
Builders brought big ideas, turned them into live Mini Apps, and shipped them inside @Nimiq Pay. The community tested, shared feedback, and hyped each other up. Reply guys and reply girls kept the conversations going week after week.
That's what a builder community looks like.
A huge thank you to every builder, tester, supporter, and community member who made this cycle what it was. Every contribution helped make it happen.
Now, the @NimiqCommunity Council takes over for scoring.
Good luck to everyone who submitted! 💛
Captain retweeted
Group vault is available!
Everyone saves toward the same purpose, but each member keeps an independent savings position.
The Circle provides the shared goal, progress and accountability. The vault protects each person’s contribution according to the rules agreed
Captain retweeted
You try to inculcate the habit of saving, but you just can’t 🥲
Let LockedIn those funds
Let it tell a story!
#makesavingsfun
Captain retweeted
run this on your repo
trust me.
With the recent wave of vulnerability disclosures, it’s a good time to take a closer look at your own code.
Turn your coding agent into a team of security auditors with the open-source skill that seeded Cloudflare’s vulnerability discovery harness.
The 6 phase approach:
1. Map the codebase
2. Hunt for vulnerabilities
3. Challenge each candidate
4. Record the findings
5. Verify the findings
6. Report what’s confirmed, rejected, or still needs validation
Start your hunt here:
github.com/cloudflare/securi…
Captain retweeted
Stop frying your brain with endless short form content. Read long, complicated, books. Especially novels. Cultivate the ability to think deeply. To focus for long periods. Stare into space and enjoy boredom. Do tasks without any media playing in the background. Resist the urge to reach for your phone every time you feel uncomfortable. Get used to being with uncomfortable emotions instead. Wonder and think about the questions you have instead of asking AI. Become deeply present with everyone around you. Your ability to focus, pay attention, to think deeply, is one of your most valuable assets. Reclaim the immense beauty of experiencing your life directly instead of living it through a screen.
Captain retweeted
try mathua.com
Captain retweeted
The @SolanaFndn monthly roundup is out. And while we get ready for the C6 kickoff on October 19, let’s look at September on @solana through the eyes of people who write and audit Rust.
Here’s what we pulled from it ↓
Captain retweeted
If you want a real mental model of how the internet moves your data, start with the 20-byte IPv4 header (most engineers have never looked inside):
• TTL: stops packets from looping forever (decremented by every router)
• Protocol field: what holds the layers together (6 = TCP, 17 = UDP)
• Identifier + flags + offset: how routers break up packets that are too big
• Header checksum: must be recomputed at every hop because TTL changes
TCP and IP both have checksums, but they protect different bits.
Then IPv6 delivered the verdict: fragmentation, header checksum, and options are gone. Fixed 40-byte header, addresses 4× larger.
Even if you use IP every day, do you know why routers never reassemble fragments and leave that job to the end hosts?
Full breakdown in the latest issue of @EngPolymathic
The 185th issue og the Polymathic Engineer is out.
This time, we complete our series of articles about IP addressing:
- The IPv4 datagram format
- Fragmentation and MTU
- Why a checksum at two layers?
- IPv6: what they fixed
Read it here:
newsletter.francofernando.co…
Captain retweeted
Everyone tags @MichaelHirsch for a Mancer spot, but no one ever asked what they could do for Mancer.
So, I took it upon myself to build something: a live dashboard where you can:
• Check your wallet mint status
• Check any/all your wallets spots
• Check all current whitelist holders ranked with the number of spots
• Watch every ledger activity (whitelist transfer) all detailed down to transaction link.
Open: mancerdash.vercel.app
No wallet connection is required.
@MichaelHirsch @jefdiesel @0x_Ezewhite 🙌
Captain retweeted
System design has no right answers, only trade-offs.
Here are 15 of the most common ones every engineer should know:
1. Scalability vs performance (handle more work vs do each task faster)
2. Vertical vs horizontal scaling (more powerful hardware vs more servers)
3. Latency vs throughput (fast individual responses vs more tasks over time)
4. Monolith vs microservices (a single unified application vs many small independent services)
5. Stateful vs stateless architecture (remember user sessions vs treat each request as independent)
6. Synchronous vs asynchronous processing (wait for each task to finish vs move on and handle results later)
7. Batch vs stream processing (process data in chunks vs handle it as it arrives)
8. SQL vs NoSQL (structured data and strict schemas vs flexibility for varied data)
9. Normalization vs denormalization (no duplicated data vs faster reads with some redundancy)
10. Consistency vs availability (up-to-date data everywhere vs a system that's always up)
11. Strong vs eventual consistency (immediate accuracy on all nodes vs a short delay in exchange for availability)
12. Read-through vs write-through cache (cache data when it's requested vs write to cache and database together)
13. TCP vs UDP (reliable and ordered delivery vs faster but possibly unordered)
14. Long polling vs WebSockets (a request that waits for data vs a continuous two-way connection)
15. REST vs GraphQL (standard HTTP methods vs querying exactly what you need)
The real skill isn't picking a side.
It's knowing exactly what you're giving up with every choice.
Which trade-off are you struggling with the most right now?
Captain retweeted
If you are a developer who likes to learn by doing, these 7 legendary GitHub repositories are gold:
1. Build your own X (525k stars)
Step-by-step guides for building your own database, git, docker, or text editor from scratch.
github.com/codecrafters-io/b…
2. Public APIs (450k stars)
A huge list of free APIs for your next side project.
github.com/public-apis/publi…
3. Developer Roadmap (361k stars)
Interactive roadmaps for backend, frontend, DevOps and more.
github.com/kamranahmedse/dev…
4. Project-based learning (273k stars)
There are tutorials that show you how to make real applications.
github.com/practical-tutoria…
5. Computer Science from OSSU (206k stars)
A complete CS curriculum from free online courses.
github.com/ossu/computer-sci…
6. Tech Interview Handbook (141k stars)
Practical content for every phase of a tech interview, from application to negotiation.
github.com/yangshun/tech-int…
7.Awesome Machine Learning (73k stars)
A curated list of machine learning frameworks and libraries, organized by language.
github.com/josephmisiti/awes…
Which one are you using right now?
Captain retweeted
You’re probably storing your users’ phone numbers, email addresses and home addresses in plain text.
If someone gains access to your database today, they’ll read them just as easily as you can.
The scary part?
Many developers don’t realize this can become a security issue, a compliance issue, and in some industries, a very expensive legal issue.
This thread will give you lots of insights towards what you need to know and not.


































