👨💻 coding for nearly a decade, ditched the 9-5 to go solo.
I post about my progress, coding, marketing, etc.
Even an 18yr vet who boosted TypeScript 10x was laid off.
Attending meetings after being told not to? Why?.....
Don't fall into their servile mindset..it just validates them.
If no one's safe than bosses don't know good leadership..
Even an 18yr vet who boosted TypeScript 10x was laid off.
Attending meetings after being told not to? Why?.....
Don't fall into their servile mindset..it just validates them.
If no one's safe than bosses don't know good leadership..
Working on projects with that US date style is super annoying.. #buildinpublic
Working on projects with that US date style is super annoying.. #buildinpublic
Is Microsoft back to its old tricks?
Reports suggest they're blocking VS Code forks like Cursor from using official extensions...
Is the tech giant reverting to its infamous "Embrace, Extend, Extinguish" strategy?
Is Microsoft back to its old tricks?
Reports suggest they're blocking VS Code forks like Cursor from using official extensions...
Is the tech giant reverting to its infamous "Embrace, Extend, Extinguish" strategy?
Looking for an alternative to tryastro that’s in a similar price range.
I’m on Linux, so no Mac apps for me—emulators didn't work.... Need a simple App Store keyword tool. Competitors are too pricey.
Suggestions?
Looking for an alternative to tryastro that’s in a similar price range.
I’m on Linux, so no Mac apps for me—emulators didn't work.... Need a simple App Store keyword tool. Competitors are too pricey.
Suggestions?
Teams treat Scrum like gospel, but it's not. Every team's different—adapt it to your style. For example, skip daily standups if they are not necessary that particular day.
Mold Scrum to fit, and your team's vibe will improve.
Teams treat Scrum like gospel, but it's not. Every team's different—adapt it to your style. For example, skip daily standups if they are not necessary that particular day.
Mold Scrum to fit, and your team's vibe will improve.
① Mock non-Vim users
② Build compilers on weekends
③ You don't know programming, if you don't know C
④ Brag about how your AI models runs only locally
⑤ Everyone else's code "unreadable" while yours is "art"
① Mock non-Vim users
② Build compilers on weekends
③ You don't know programming, if you don't know C
④ Brag about how your AI models runs only locally
⑤ Everyone else's code "unreadable" while yours is "art"
* Get a degree
* Get a 9-5 job
* Get a suit & tie
* Get a promotion
* Get Married at 21
* Buy a House at 25
* Have 4-5 Kids & 1 dog
* Retire at 60 with pension
2025: Survive... #buldinpublic
* Get a degree
* Get a 9-5 job
* Get a suit & tie
* Get a promotion
* Get Married at 21
* Buy a House at 25
* Have 4-5 Kids & 1 dog
* Retire at 60 with pension
2025: Survive... #buldinpublic
1/ What do you think about calling this variable userId?
2/ What's the rationale behind this implementation?
3/ Have you considered an alternative approach here?
4/ Could this method be clearer with inline comments?
1/ What do you think about calling this variable userId?
2/ What's the rationale behind this implementation?
3/ Have you considered an alternative approach here?
4/ Could this method be clearer with inline comments?
1️⃣ Never update your skills.
2️⃣ Blame everyone else for bugs.
3️⃣ Write code only you understand.
4️⃣ Avoid teamwork.
5️⃣ Ignore feedback entirely.
1️⃣ Never update your skills.
2️⃣ Blame everyone else for bugs.
3️⃣ Write code only you understand.
4️⃣ Avoid teamwork.
5️⃣ Ignore feedback entirely.
DeepSeek is free until the server gets busy after a couple of questions... I'd rather pay monthly for a service that actually works, than use one that fails when you need it... #buildinpublic
DeepSeek is free until the server gets busy after a couple of questions... I'd rather pay monthly for a service that actually works, than use one that fails when you need it... #buildinpublic
#buildinpublic
#buildinpublic
I often see devs use design patterns wrong in code reviews. They introduce them too early, making code more complex. Don't start with Factory/Strategy etc. Understand the problem first, code raw, then simplify if necessary
I often see devs use design patterns wrong in code reviews. They introduce them too early, making code more complex. Don't start with Factory/Strategy etc. Understand the problem first, code raw, then simplify if necessary
1️⃣ Think systems, not just code
2️⃣ Debug like a pro
3️⃣ Embrace imposter syndrome
4️⃣ Take ownership
5️⃣ Master your tools
6️⃣ Communicate clearly
7️⃣ Say no when needed
8️⃣ Understand the business
9️⃣ Automate repetitive tasks
🔟 Learn to guesstimate work
1️⃣ Think systems, not just code
2️⃣ Debug like a pro
3️⃣ Embrace imposter syndrome
4️⃣ Take ownership
5️⃣ Master your tools
6️⃣ Communicate clearly
7️⃣ Say no when needed
8️⃣ Understand the business
9️⃣ Automate repetitive tasks
🔟 Learn to guesstimate work
Every dev should write bad code. It's how you learn good practices. Embrace the messy drafts and "What was I thinking?" moments, they're steps to improvement.
And just know that your code will never be perfect, so don't aim for it.
Every dev should write bad code. It's how you learn good practices. Embrace the messy drafts and "What was I thinking?" moments, they're steps to improvement.
And just know that your code will never be perfect, so don't aim for it.
As a developer, negotiating with clients can feel daunting. But it's also your chance to ensure projects succeed without burnout or feature creep. Here's a step-by-step guide to navigating these discussions effectively //THREAD// 👇
As a developer, negotiating with clients can feel daunting. But it's also your chance to ensure projects succeed without burnout or feature creep. Here's a step-by-step guide to navigating these discussions effectively //THREAD// 👇
If you need a comment to explain it, maybe refactor instead..
If you need a comment to explain it, maybe refactor instead..