You might like
Seems some incels like C++ more than warranted
A thread 🧵 Some things to keep in mind if you're considering investing in crypto assets: MUST HAVE HAT $WIF
Writing programs in GW-BASIC, obviously
10 years old boy writing program in python...what were you doing at his age?
If you look for a reason to hate a person, eventually you'll find it. If you look for a reason to celebrate a person, eventually you'll find it. The former leads to resentment and destructive cynicism. The latter leads to happiness and growth for you and for those you celebrate.
“Guaranteed maximum fragility”
Folks seem to tune software development for a desired output rate. That's a disaster. Here's why, what to do instead, and (at the end) a speculation about an unhelpful belief that might underlie this behavior.
You can have the fanciest CI/CD pipeline on the planet, but if you don’t push to trunk a few times a day at least, you’re not integrating continuously. CI is an attitude, not a pipeline.
One of the most valuable skills for engineers of any level of seniority is learning how to be very productive when dealing with extremely “messy” systems or codebases. People who have this skill are often very successful in pretty much any conceivable scenario.
This is the best satire I've ever seen on the incredible misalignment between computer science majors, corporate software interview practices, and actual application engineering. So mad I didn't write this myself darkcoding.net/software/a-day…
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." -- Brian Kernighan
"Code perfection is like eventual consistency; it's something that you should constantly move towards, yet may never attain." #wisdom
New article: Against consistency ift.tt/3wbJsIV
Do not just talk about problems in a retrospective. Spend some time to say thank you and celebrate accomplishments. Hear more from @paulocaroli in episode 37. techleadjournal.dev/episodes/37
I feel like "legacy code" is a pejorative and I wish it wasn't. I find the challenge of adding features and refactoring existing code to be a very fun puzzle, and I wish there was a label that reflects that
– We don't write tests. – Why? – Because we don’t have time for it. – Why? – Because there is too much work and pressure. – Why? – Because we don’t move fast enough. – Why? – Because changing software has become difficult and risky. – Why? – Because we don’t write tests.
I'm always surprised at how few developers actually do this. "As disappointing as it may be, keeping up to date with technology is your responsibility, and if you can't sneak in some time for self-improvement at work, you'll have to do it on your own time."
A very insightful thread about the negative effects PRs can have on team morale.
So if I were *designing* a way to erode safety & trust, I'd choose an async, text-based process in which any one person can derail others' work by nitpicking it. Show off knowledge. Re-fight a lost battle. Assert authority. Defend turf. Cover up insecurity. Call it code review.
United States Trends
- 1. Broncos 34.5K posts
- 2. Raiders 44.2K posts
- 3. Bo Nix 7,742 posts
- 4. #911onABC 22.7K posts
- 5. Geno 7,641 posts
- 6. AJ Cole N/A
- 7. #WickedOneWonderfulNight 2,919 posts
- 8. GTA 6 83.8K posts
- 9. Chip Kelly N/A
- 10. eddie 44.2K posts
- 11. #TNFonPrime 2,670 posts
- 12. #RaiderNation 2,726 posts
- 13. Crawshaw N/A
- 14. tim minear 2,695 posts
- 15. Al Michaels N/A
- 16. Cynthia 36.7K posts
- 17. Jeanty 4,265 posts
- 18. #RHOC 2,002 posts
- 19. Thornton 2,577 posts
- 20. Ravi 15.5K posts
Something went wrong.
Something went wrong.