HigginsNinja

Too many companies get stuck with expert beginners in lead positions. I wonder how many of those companies have actual hope for change.

SO many shops just adopt Redis as a cache store after seeing the benchmarks and local tests. This needs some more attention. I have seen a few systems crash and burn from bad implementation of a caching layer.

This is phenominal. I wish I got moving as early as this kid. Watch him for big things.

I have been able to combine basically any framework or library with angular for DOM manipulation and other related tasks. You just need to wrap the libraries with angular, which is fairly trivial to do for your selected subset of functionality.

Either demand will explode again, or there won't be much new adoption outside of proof of concept projects. They basically will be losing much of the continuity other frameworks have.

I personally/professionally will consider using CanJs and EmberJs from now on.

I agree with it in terms of generally desired skill sets. Angular rose to prominence very quickly and Node has had a very steady grassroots climb. Backbone has been on the decline for a while now. I don't think React has the klout to really become a commonplace skill. We will see what happens with Angular after 2.0 though.

These are actually really good bits of advice.

I agree with you, but there is still convincing hiring managers that it's okay to hire someone who technically doesn't have professional experience in ASP.NET MVC when the position is primarily that.

Here is a company I have worked in. They have legacy systems that are pretty heavily Web Forms and there is a lot of SQL work too. They are making the transition to MVC and ORMs in a lot of the legacy stuff.

http://careers.stackoverflow.com/jobs/75235/principal-softwa...

Hope it goes well for you.

I definitely do not have the level of experience that you have so take this with a grain of salt. I have seen and worked in a lot of companies that have a very heavy portion of their code base in web forms. Many of these companies have been working to transition to MVC but it takes a longer time the larger your legacy beast is.

I would suggest finding a job where you can leverage your experience in .NET Web Forms, while picking up the pedigree for MVC.

He is saying that Node is not a JavaScript framework. It is technically a back end scripting language. So maybe you would do well with a better umbrella term like skills or tools.

Lowering the barrier to taking good screenshots sounds like a good mission to me. It's definitely not a glorious one but I for one welcome the possibility that most bug reports come with corresponding screenshots.

We are approximately half remote actually. We just treat every interaction as if everyone were a remote employee.

Obviously not EVERY reaction, but if that is the default, it's quite easy to sustain.

True, maybe a good follow up to this would be some use case studies. It would be so easy to pick any given set of companies for my narrative though. I feel like that is just as dismissable.

This article is more of a narrative on when you have non technical management who is flexible, but just doesn't know or care about the technical aspects of your job. They just want it to work.

Absolutely, if you have buy in from management to attack the technical aspects it's a much better environment overall.

I mean to speak more to the situations where you have non technical management, or at least those that don't understand the repercussions of bad technical decisions.

In those situations, you need to take it on yourself to make sure you're handling the technical balancing act yourself.