Shoot me a message, I am VP of Engineering at large European software logistics company, where I had exactly the same challenge (outsource vs insource). Email is in my profile.
Curious, I am pro nuclear as well, looking at the technological benefits, but how are we practically going to handle nuclear waste that will be there for thousands of future generations to handle?
If that’s true why would be this obstructionism be there? It does not make any rational sense if we can use nuclear to win us time until we have working fusion and/or wind/sun/etc energy implemented.
> If that’s true why would be this obstructionism be there? It does not make any rational sense if we can use nuclear to win us time until we have working fusion and/or wind/sun/etc energy implemented.
Not tested them both: I work with annual billing for my SaaS. The pricing page shows monthly prices, which works well for me. Customers buy a contract for a year which they can cancel at any moment. Obviously the remaining months within that contract year will not be refunded. Note that the SaaS is only 300 euros a year so your mileage may vary. (B2B market)
newsat13 wasn't complaining about using conventions. newsat13 was complaining about how Rails uses black magic with conventions.
I can't speak to Rails, but I've worked in other codebases that used reflection to dynamically attach different pieces of code together. It was hard to trace code because I couldn't do a search for the value being generated nor could I use the static analysis to find the value. I had to manually trace through the whole stack to find the bit of reflection that was generating a value.
I've never worked in a codebase like that, but in all my years of helping people with Ruby and Rails I've concluded that reflection is a code smell. It's one of those things that is taught in CS and winds up appearing where conventions might not have been immediately apparent, a fallback to training.
In my experience being productive is more a matter of setting a clear scope of goals on which I'm going to focus on the next X months. Other than the strict necessary tasks that might interrupt activities related to these goals, no extra goals may be added until one is finished. After that, at the beginning of each day I decided what micro-tasks I want to do (write paragraph X of paper, fix bug Y in project Z) and I don't go home until I am done. Everyday it seems like I am only doing small tasks but after time these tasks add up and I finish big projects. Big projects/goals are not finished over night, you need time. It's easy to get demotivated when there are big tasks ahead. The key is to chop them into do-able, reachable tasks and you hold yourself accountable to fix these tasks no matter what.
Exactly the reason why I did a Bachelor in International Business Administration and a Master in Computer Science (Embedded Systems)! I feel that the gap in between is a good niche to be in. I have to say that there are some education programmes where the focus is on IT management that try to fill this niche too although I have some doubts about how effective it is to study IT management in itself.
