• 0 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle










  • After many failed attempts at TDD, I realized/settled on test driven design, which is as simple as making sure what you’re writing can be tested. I don’t see writing the test first as a must, only good to have, but testable code is definitely a must.

    This approach is so much easier and useful in real situations, which is anything more complicated than foo/bar. Most of the time, just asking an engineer how they plan to test it will make all the difference. I don’t have to enforce my preference on anyone. I’m not restricting the team. I’m not creating a knowledge vacuum where only the seniors know how yo code and the juniors feel like they know nothing.

    Just think how you plan to test it, anyone can do that.



  • There are already some attempts but I don’t think it will work, harmful even. Best case scenario, the AI can understand the code as well as a senior engineer from another company. All they can know without the context is what was changed, which is useless. We need the reason why the commit was made, not what was changed. The info is not there in the first place for the AI to try to extract.



  • CEOs tends to think they’re special. They do not think they are there because of right time right place.

    I work in tech and I have seen how a small change in organization structure, such as a Product Manager leaving, or adjusting how Product, Engineering and Marketing working together, having a huge impact on how the business operates. Yet most CEOs think the company is where they are because of their own decisions. It’s quite the other way around: CEOs suggesting stupid policies and other people cleaning up the shit, like “let’s all go back to office because I’m lonely here”, despite majority of employees work remotely from another fricking country.