#Adam automailer software#
#Adam automailer code#
#Adam automailer windows#

#Adam automailer code#

They really don’t need to attempt to keep up with the absolute latest and greatest, because if you’ve had experience working on large pieces of code, then you can work on other large pieces of code and that knowledge transfers. I’m actually sympathetic to Academia in that situation. I use this framework, but now my other company is using a different framework.

And that’s just a general problem in the industry you get that switching jobs also.

Certainly, people come out of school - even if they did study web design (which they may not have done) and used a JavaScript framework (which they may not have done), there’s probably something new that’s come along in the last six months, that makes their knowledge obsolete. Well, the state of the art issue is also there.

#Adam automailer software#

At this point they have thousands of developers on them, and this stitching together and maintaining it over different cycles of engineers as people leave and new people join really becomes critically important, and it’s just not something people are prepared when they go to school and study computer science or software engineering.

#Adam automailer windows#

In that environment really any language is fine, and everybody can meet in a room to discuss things, so stitching together large pieces of software from individual components doesn’t really happen, and the original authors of the software are there for the entire duration, so they just know how it works the documentation is not really an issue.Īnd then you get into the industry and you’re working on these large pieces of software – obviously, at Microsoft I worked on Windows and Office, two very large pieces of software. You tend to write small pieces of software, two or three people working for a semester, and then you’re done. A lot of it starts with what I consider the basic problem with software, which is that when you’re in school, Academia doesn’t really study industry, and you don’t get a lot of advice on this. It made me realize that across the industry you have the same issue - people just don’t really know if the way they’re writing software is actually correct, if they’re using the right language, as I said, or the right tools and technologies. They just tended to use the same technique and language and process that they’d used before, which might have been something that the person who created the group happened to like, or had some experience with… And from our central perspective in Engineering Excellence we could tell that some of these processes were better than others. I realized that even inside Microsoft, which people may think of from the outside as having this single way of writing software, there were actually a bunch of different ways some were better and some were worse, but people didn’t really know.

It was quite interesting, because normally at Microsoft you only get a view of the team you work on, and this enabled me to get this view across Microsoft.

One of the more interesting jobs – I was primarily a developer, a dev lead, engineering manager, but for about five years in the middle I worked in this group called Engineering Excellence, inside Microsoft, which did training and consulting for teams internally.