137 karma · joined April 7, 2016
You will still have to read the boilerplate of course.
Of course it makes watching the game a worse experience.
We are now using a mixture of 3 different dependency injection frameworks, manual dependency injection, and instantiating dependencies in the constructor.
It's the same reason Java, with all its boilerplate, is so widely used.
In practice, this is pretty similar to how you maintain compatibility with old clients in JSON. But with protobuf, you have the schema file to make code reviewing this kind of change easier.
More work means
- more employees needed
- more direct reports for managers
- more jobs for x technology
- more people learning x technology because of those jobs
- more StackOverflow questions for x
- more companies using x technology because it's "easy to hire for"
- more money to be made in teaching x
- more learning material for x
For example, Google Closure Compiler can take
function hello({name}) {
alert('Hello, ' + name);
}
hello({name: 'World'});
and compile it into alert("Hello, World");No more Emacs pinky.
Depending on the company and product, it might make sense to focus on performance or building a shared component library. In our case, the average team's productivity was far below where I believe it should be because of dull tools. Figure out where your company needs improvement the most and make it better.
If you have the leverage, 17 people in daily standups is a good problem to fix.
Depending on your use case, you may have to do a lot to work around protocol buffers not being self-describing. I haven't seen a good description of the problem online, but if you find yourself embedding JSON data in protobufs to avoid patching middleware services constantly, you should look at something like Avro or MessagePack or Amazon Ion.
I'd recommend Spacemacs (even if you're not using evil) if you're new to Emacs and want to see how different and powerful a fully customized Emacs is when compared to the bare-bones experience of stock Emacs.
Perhaps you would prefer something like Ion: https://amzn.github.io/ion-docs/guides/why.html