Recent Changes - Search:




edit SideBar


If you do not know what Software Craftsmanship is, first read the links:

Otherwise I feel like I really need to add a few things:

  • Are you a Software Craftsman or Software Laborer?
- A Software Craftsman loves software, wants to continue getting better at it, strives to perfect the craft, and wants to help others do so too.
- If you love what you do its not work and its interesting and new problems to solve excite you.
- Software Craftsmanship is about rejecting an elitist attitude and is at its core the most humble position possible to take in software.
- You must first acknowledge that you don't know everything and be open to learning, in order to learn and think of yourself as on the path to it.
- Software Craftsmanship's goal is not to make others feel bad about their code.
- A Software Craftsmanship's goal is to teach programmers how to write better code, and behave better as professionals.
- We feel that the software industry urgently needs to raise the bar of professionalism, and so we out to be the sort of change we want to see in the world.
- A Software Laborer just wants the paycheck and doesn't care about code when they are not getting paid to.
- If you are only a A Software Laborer, please do yourself and the rest of us a favor and quit the software industry.
- Nobody should spend the majority of the day doing what they do not love. And this lack of love will show in your work.
  • Use the right tool for the job.
- TFS is usually the wrong tool for builds.
- MongoDB is always the wrong tool for everything.
- Better Caches exist.
- Better Database's exist.
- It is insecure by design and should be considered a security threat to the network it is hosted on.
- No other roles are left for MongoDB because its broken by design compared to the available alternatives.
  • Continuous Integration is a strict requirement, not a luxury.
    - Its basic plumbing you need before you start writing code.
  • Technical debt is not a badge of honor; It means you and your leadership failed.
    Technical Debt happens. Facing it is the first step to removing it.
  • Staying until 1am during a production release that started at 8pm is not a badge of honor; It 's Technical Debt.
  • Every project should have a postmortem.
    You can only learn if you first admit you do not know everything.
Edit - History - Recent Changes - Search
Page last modified on April 17, 2016, at 03:12 PM PST