the0takuc0mrade.dev @junep059

Learn something new every day. Your brain can handle a very limited amount of genuinely new information at a time. You are fundamentally limited by the rate at which neurons can form connections. Your "daily learn budget" is use it or lose it. So use it.

@winsznx Congratulations

1 - I did not expect to get a 100k+ impressions on a post about random AI napkin math I did in my head while taking a dump. 2 - I expect to be paid about $90 in X creator money for the level of reach this got. 3 - One DGX Spark costs $4,600 4 - I can pay for one machine by sending ~51 tweets like this. 5 - After purchasing the Spark, purely funded by X payouts, I'll create content about using the machine and farm more engagement. 6 - What did I miss?

Jeffrey Scholz @Jeyffre

a week ago

1 - So GLM 5.2 is 700b parameters (ish) 2 - 4x DGX Sparks can supposedly handle up to 700b parameters (give or take) 3 - GLM 5.2 is supposedly in striking distance of the performance of GPT 5.5 and Opus 4.8. In my brief tests, it's really not shabby at all. 4 - So for $20k,

279 113 2K 520K 635

@TheGreatUthman @Wizarab10 No be lie

FROM NOW ON ADDRESS ME AS CHAMP! 🧡💙

The number one question I get asked: "What field of software/blockchain should I study for the best job prospects?" "Should I do Rust, cross-chain, privacy, distributed systems, security..." But that's not what the real question is. The question behind the question is often: "Is there a shortcut I can take to earn good money in software with relatively little effort?" Here's why I know the hidden question often exists: If you want a guaranteed high salary in software, just be really good at it. Solve hard problems, prove you are a chad, and money will rain down on you. Want to make a lot of money? Work at X or Goldman Sachs or something. But of course -- that requires a huge amount of hard work to get employed at a place like that. That is the hard work that a lot of people try to sidestep with a shortcut study plan. If you are genuinely unsure of what to study, study the CS fundamentals. Topics are easy to learn if you already know a related topic, and CS fundamentals are related to everything. When the day comes to lock in and pick a domain-specific subject, having the fundamentals down will make it easier to learn.

@judicodes Hi hi

Have you registered yet, or are you waiting till 2027 to add “Learn a tech skill” to your New Year resolution again? Don’t let another year pass you by. Register NOW, not later. 👇 web3bridgeafrica.com/register #TechEducation #Web3Bridge

One of the big killers of developer upskilling is unrealistic expectations. The fundamental mismatch is that human brains cannot internalize new information as fast as many engineers would like. This leads to a cycle of aggressive learning, burnout, forgetting, and spinning wheels. Most people cannot realistically learn genuinely *new and unfamiliar* material for more than 1 hour a day, and even that is generous. Your brain needs time for new information to sit in the background while it connects to prior knowledge. Now, you can learn a lot more than 1 hour of *similar* information to what you already know, or 1 hour of *review*. For example, you could learn a new programming language in a weekend if it is close to one you already are fluent in. If you are trying to learn Rust (for example), and you already know some of it, then it is possible to be productive for 3 hours struggling with it if you have a baseline. That's because a significant amount of the three hours is spent on review. However, you cannot engage for a long time on a subject that is very far from what you already know. As an extreme example, think about trying to learn Russian if you don't even know the Cyrillic alphabet. Your brain will be cooked after 20 minutes. The problem is that learning *similar* information doesn't feel as "fast" as learning *new and unfamiliar* material. Many developers place an expectation on themselves that they should be internalizing copious amounts of *new and unfamiliar* information because the space moves so fast. But that is not realistic. By *learning* I mean really engaging with the material, not passively consuming it (of course you can passively consume for more than an hour, but that doesn't get you far).

Hey devs! 👋 Quick question, how are we actually sharing production keys, .env files, or database passwords with teammates these days? We all know pasting them in Slack or Discord isn't ideal, but password managers can feel like overkill for a quick handoff. I’m working on a research-driven tool called LockShare to build a better alternative, and I’d love to get your raw feedback on how you handle this and what your ideal workflow looks like. It’s a super quick, entirely multiple-choice questionnaire: docs.google.com/forms/d/e/1FAI… Appreciate your time and insights!

I've yet to see a learning technique as powerful as explaining things in your own words. The numerous benefits include: 1. Catching your own knowledge gaps is easier, as they stand out like a sore thumb. You quickly realize you don't know as much as you thought you did. 2. You are far more likely to remember what you learn, as good explanations create compact mental models. It really sucks to spend 10 hours studying something and not remembering it 3 weeks later. 3. It forces spaced repetition as it is very unlikely you will be able to explain things on the first try. The very fact that it requires multiple attempts forces you to space things out. 4. While you can do it alone, it's more effective with another human. This creates natural accountability. 5. You don't fool yourself into thinking you understand something when you really don't. I've seen this play out over and over. Someone "thinks" they understand, say, Uniswap for example, then they fall flat on their face trying to explain it. This has a name by the way -- "Illusion of Explanatory Depth" 6. You get free interview practice. Interviews are about explaining something you know, and that in and of itself is a skill. 7. You keep your communication skills and technical skills in balance. You don't become that tech chad who can't progress in their career because they can't convey their ideas to other people. 8. You build your AI skills. If you can't explain to an AI what you want, you won't get it. I used to spend my time lecturing. Now I just ask people to explain things in their own words (and ask probing questions to make sure I'm not getting a memorized recitation). Explanation-focused learning isn't a silver bullet. You still need to drill and get your hands dirty with low-level details. But those should be seen as a step towards being able to explain the subject yourself.

GM guys! Another week to scale up and work smart. Have a productive week ahead!🙂‍↔️

Registration for the final Web3Bridge Cohort of 2026 closes THIS WEEK! ⏳ Choose your track 👇 ✅ Web2 Basics— ₦30,000 ✅ Web2 Advanced— ₦30,000 ✅ Solidity (Web3) — ₦50,000 ✅ Rust — $100 ✅ Zero Knowledge (ZK) — $100 Invest in your future this week. Your future self will thank you. 🚀 Register now 👇 web3bridgeafrica.com/register

keyboard_arrow_left Previous keyboard_arrow_right Next

Rejected from YC and A16Z. Only up from here. Galatians 6:9

Ciara @CiaraACade

a month ago

Next steps with a16z let’s freaking go

11 1 124 34K 14

@lenientttt @ronpishmimimi My GOAT 🐐

The tiktokization of Twitter is upon us.. This changes the attention game in so many ways..

hmm, this is interesting. i'm curious how teams are actually handling sharing private keys, passwords, and even files. the quoted tweet has a short questionnaire, check it out if you can. 🫶

@

57 years ago

0 0 0 0 0

@deolarepublic Gm ser, I'm in your DMs 🙂‍↕️

@deolarepublic Hi ser, I sent you a direct message, can you check it please?