你可能會喜歡
Been tweaking trying to fix a bug for a day. Have just moved into the "wait, how did that ever work?" stage
Picard management tip: Don't negotiate absurd schedules with engineers. Encourage truth telling and reasonable time estimates.
My impression is that most tutorials on mocking and mocking frameworks lead with how to stub code for tests than how to actually use mocks for testing. Such priming might explain many common misunderstandings around mocking, as well as the parlous state of many mock-based tests.
You could not be promoted without showing cross team impact and the easiest way to do that was build a tool, get another team to use it, and then abandon support. What you incentivize is what you get.
Your .net code does not need 15 projects with a class per command and query. You don’t need an interface for everything either. It’s amazing to read extremely simple samples using .net vs node vs go. It seems our ecosystem is attracted to complexity... #dotnet
"Monoliths are the future because the problem people are trying to solve with microservices doesn’t really line up with reality", I aspire to such savage language as that which flows from @kelseyhightower. PREACH BROTHER! 😂❤️✊ changelog.com/posts/monolith…
Sometimes I read or hear someone say that what a particular codebase needs is more documentation/commenting. Be careful what you wish for, you may get it. 'More' is rarely what you want; 'better' is normally what you want. Don't wish for quantity when what you need is quality.
So, my thoughts on engineering performance management have always been a bit idiosyncratic, but Matt's tweets today have me reflecting, so... storytime. 1/
I've seen this talk, and not surprisingly it's close to my own thinking and experience. Can you summarize the evolution in your thinking?
Talking about “clean code” is a waste of energy. Let’s instead talk about pure and compositional code cause those have actual definitions and value.
Oh for fucks sake 🙄. Don’t sacrifice your 20s – or any other decade of life! – on the erroneous belief that unless you work round the clock, you’re not going to be “successful”. The world is full of people who were all work and now are all regret.
the "Documentation Rule" is that you read a test in order to understand the code. The test is self-explanatory and explains the code (context, purpose, & intent; not mechanism). You should never have to read the code in order to 'understand' a test. That's a violation.
Just paused Star Trek Discovery to read the code Burnham is working on, and it’s just the Win32 APIs. Looks like Starfleet runs Windows.
Every position we open at Basecamp receives hundreds of applications. Our secret recipe: 1) Pay well, 2) Hire remotely, 3) Explain the position thoroughly, 4) Have a reputation for being a good place to work, 5) Stop dog whistling overwork with “strong work-ethic” bullshit.
Nearly every entrepreneur I talk so says hiring is their biggest challenge. The world is starving for competent people with a strong work-ethic.
The Stateless Motto: Make state someone else’s problem.
Imagine a 1 million line project, and you contributed just *one* line of code. Except it was the most important line ever and changed everything for the industry and you got a honorary PhD and a Wikipedia page.
Number of lines of code written is not a measure of your value to a project.
United States 趨勢
- 1. #StrangerThings5 238K posts
- 2. Thanksgiving 667K posts
- 3. BYERS 53.4K posts
- 4. robin 89.3K posts
- 5. Reed Sheppard 5,665 posts
- 6. Afghan 281K posts
- 7. Podz 4,320 posts
- 8. holly 62.7K posts
- 9. Dustin 88.6K posts
- 10. National Guard 656K posts
- 11. Vecna 56.5K posts
- 12. hopper 15.5K posts
- 13. Jonathan 73.7K posts
- 14. Gonzaga 8,445 posts
- 15. Lucas 82.2K posts
- 16. Erica 16.9K posts
- 17. noah schnapp 8,764 posts
- 18. Nancy 66.9K posts
- 19. Tini 9,324 posts
- 20. Joyce 30.9K posts
Something went wrong.
Something went wrong.