4 ms·

I used to think that resume driven development was nothing but a curse but I've softened my stance on it a little. Realistically developers are compensated by

I used to think that resume driven development was nothing but a curse but I've softened my stance on it a little. Realistically developers are compensated by a range of different things - free gourmet meals might be one - another even more important one being career development. If you let developers who want to use kubernetes use kubernetes even if it's not strictly necessary it might be a net positive for the company. Hell, even if kubernetes is a slight negative compared to the simpler equivalent it could be a net positive because it gave somebody who wanted it a career boost from experience with a "hot" technology which made them happy. Now, only if RDS is going to cause a massive headache would I be seriously against it - provided we walk into this situation with open eyes.

jjeaff 8y ago
There's also something to be said about not having to scramble to configure things once you outgrow that simple VM setup. Obviously, you shouldn't prematurely optimize, but you also shouldn't wait until you are getting multiple hours of downtime every day while you are scrambling to get a better solution in place. And I think many times we underestimate the server power we will need as we grow. After a few hundred users I used to extrapolate that I would never really need more than a large VM and database instance. But then we added more and more functions and features and more and more computer power is needed per user now. Then we started running into issues where certain procedures would take too long so they need to be queued, well then you have the overhead of a queuing system and on and on. It's kind of the same thing that happens with companies as you hire employees. You think, oh, we have 5 developers now. We will never need more than 15 devs and some customer service and sales. But then you need someone to handle HR, and maybe a bookkeeper, and then people to manage the non developers, and then someone to manage the project and it just kind of grows exponentially.
nwsm 8y ago
>resume driven development I haven't heard this term before. I love it

jjeaff 8y ago

There's also something to be said about not having to scramble to configure things once you outgrow that simple VM setup. Obviously, you shouldn't prematurely optimize, but you also shouldn't wait until you are getting multiple hours of downtime every day while you are scrambling to get a better solution in place. And I think many times we underestimate the server power we will need as we grow. After a few hundred users I used to extrapolate that I would never really need more than a large VM and database instance. But then we added more and more functions and features and more and more computer power is needed per user now. Then we started running into issues where certain procedures would take too long so they need to be queued, well then you have the overhead of a queuing system and on and on. It's kind of the same thing that happens with companies as you hire employees. You think, oh, we have 5 developers now. We will never need more than 15 devs and some customer service and sales. But then you need someone to handle HR, and maybe a bookkeeper, and then people to manage the non developers, and then someone to manage the project and it just kind of grows exponentially.

nwsm 8y ago

>resume driven development I haven't heard this term before. I love it