2,972 karma · joined May 16, 2007
That is my goto advice on buy vs build. If you buy, then you should be willing to change your business to fit. Otherwise you should build. The more you resist changing your business the more you should build. The more you don't want to build, the more you should be willing to adapt.
- In software engineering it is notoriously difficult to distinguish between capable and incapable companies/individuals. You basically need a very capable person to make the evaluation. But who chooses the evaluator ?
- Even a capable company can screw up by no putting the right people in the project.
- Even one person in a capable team can derail a project.
- A project needs time to ramp up, go from alpha testing to beta testing to production. A project that goes from dev to production in one night has 10x the risk of a regular project.
- 60k is very little money for such a risky project.
- Finally, The obligatory don't ever, ever trust voting software https://xkcd.com/2030/
But you can quote Larry Wall on the three virtues of a programmer. http://threevirtues.com/
- Do you have autonomy in your job ? You need to be able to do your job without having to ask for permission every five minutes. You should also have some freedom on how to do it.
- Do you feel you are getting better at your job ? Every day you need to have the feeling that you are becoming better at it. Is your job hard enough but not too hard. Too many unknowns may cause frustration. Too few unknowns make the jobs too easy and boring.
- Purpose - Do you feel that everyday you are making a difference? You need to feel that you are making somebody's life better.
This is a pretty nice approach. Congrats.
Often people are chosen in senior positions because the sell themselves. They are articulate and have "executive presence" and they seem to know what to do, but often they don't. I wish more of them were chosen because they listen, and they knowledgable and thoughtful.
1.- housing - We are outbiding each other for the same houses.
2.- health - The health systems is plain disfunctional. Quality is great but paying for it is a big problem.
3.- College cost inflation.
They on the other hand, have all their time to think and scheme on how to sell themselves and get ahead. They even have time create meetings and ask for reports.
If you are a technical person you need to be will to spend as much time as they do, and forget about your technical work. You is ok if that is what you want. Otherwise you will be in the short end of the stick.
I think there are actuarial tables where you can get an estimate based on your age. Or just mark ~75 as expected and use a different color for extra time beyond the expected.
- Annotations are overused.
- Design patterns are overused.
- Too many layers, too many abstractions.
- Using properties where a constants would be enough.
- Using concurrency when you don't need it.
Probably a cultural problem more than a technical.