“What you should know as a founder of a software company” is a nice overview of subjects, with links to learn more, for anyone who is thinking about or have already started a software company. The article goes through:
Of course, no one article can tell you everything you need to know to run a software company – there’s just too much – but this one is a good place to start.
https://www.youtube.com/watch?v=4SAkq6lsnoE
Here’s Gordon Ramsey’s documentary on the shark over-fishing and the horrors of shark finning. I’ve heard about this before, but the video left me speechless.
I’ve trained more people on the subject of pull requests than I care to remember. But I’ve never came close to explaining the best practices as well as this Slack Engineering blog post does:
Basically, your reviewer is totally missing context, and it is your pull request’s job to give them that context. You have a few options:
- Give it a good title, so people know what they’re getting it into before they start.
- Use the description to tell your reviewer how you ended up with this solution. What did you try that didn’t work? Why is this the right solution?
- Be sure to link to any secondary material that can add more context — a link to the bug tracker or a Slack archive link can really help when describing the issue.
- Ask for specific feedback — if you are worried that the call to the `fooBarFrobber` could be avoided, let them know that so they can focus their effort.
- Finally, you should explain what’s going on for your reviewer. What did you fix? Did you have any trouble fixing the bug? What are some other ways you could’ve fixed this, and why did you decide to fix it this way?
Not every pull request needs every single one of those things, but the more information you give your reviewer, the better they will be able to review your code for you. Plus, if someone ever finds a problem in the future and tracks it down to this pull request, they might understand what you were trying to do when they make a follow-up fix.
Give your reviewer all the context they need to get up to speed with your bug so they can be an informed, useful code reviewer. It’s all about getting your reviewer onto the same page as yourself.
I am not the biggest fan of shareware or other ways of limiting user rights when it comes to software, but if I had to pick one and call it my favorite, I’d go for the postcardware. Have a look at this good example:
Open source software is used in all projects we deliver. Laravel, Nginx, Ubuntu are just a few of the free pieces of software we use every single day. For this, we are very grateful.
When we feel we have solved a problem in a way that can help other developers, we release our code as open source software on GitHub.
A lot of our packages are postcardware —free to use if you send us a postcard.
I came across this Periodic Table of Software Engineering, and I think it’s an excellent visualization. For those working their way to become software engineers, it provides a nice map of skills, topics, and knowledge areas to cover. For the rest, it clearly explains why software is so much more complex than anybody thinks.