Talking write away software engineering

Conclusion Here are five more Guiding Principles I use when making technical decisions as a software engineer. You can also check out Part 1.

Talking write away software engineering

James Lewis on twitter: SE-Radio brings you relevant and detailed discussions of software engineering topics at least once a month. Welcome to another show of SE-Radio. James Lewis is a principle consultant at Softworks and calls himself a coding architect.

He is part of the technical advisory board which meets quarterly to produce the ThoughtWorks technology rater.

Engineering Questions including "Where does electricity come from"

James studied astrophysics in the 90s, but got sick of programming in fortune. Fifteen years of DBA, software engineering, design and architecture later, he believes that writing the software is the easy part of the problem. So, welcome, James on the show.

Thank you very much. So is there you would like to add to your biography?

Exceptions

I think that pretty much covered it. We wanna talk about micro services. Can you maybe start by just giving us an idea of what a micro service is?

So a micro service in my mind is a small application that can be deployed independently, scaled independently that can be tested independently and which has a single responsibility.

talking write away software engineering

So, this is on multiple axes. What would be such a single thing be? An example might be a queue processor. So I have the impression that micro services became quite popular in recent time. You have been talking about it.

Lean Startup Book

Other people have been talking about it. Why do you think is that? For me the journey starts a little while ago around four years ago where I put a lot of time at some workshops with people from various different communities and software industry.

Some of the people involved in the RESC community, the messaging community and so on. At these workshops a lot of the questions that kept reoccurring if you like were around the size of applications or seemed to me around the size of applications. So Dan North talks about replaceable component architecture.

He stresses the idea of replaceability in these systems.X Exclude words from your search Put - in front of a word you want to leave out. For example, jaguar speed -car Search for an exact match .

New tips, trends, and insights from the world's leading enterprise cloud ecosystem in sales, service, marketing, community, analytics, and apps. Facts and Fallacies of Software Engineering [Robert L.

Glass] on tranceformingnlp.com *FREE* shipping on qualifying offers. The practice of building software is a “new kid on the block” technology. Though it may not seem this way for those who have been in the field for most of their careers.

Engineering is an art and profession devoted to designing, constructing, and operating the structures, machines, and other devices of industry and everyday life. I for one think this is a great change, and a brilliant post.

Absolutely, less time delightedly exploring still more abstruse mistake-theory-legible problems (although these are fun and the theory that total unity is possible feels good) in favor of more time spent on projects such as, “which candidates are really fighting for the people vs.

just astroturfed shills” . No matter your security, the human element at your business is vulnerable to hackers. Learn 9 steps to tighten your security against social engineering attacks.

Absolutely No Machete Juggling » Software Engineering Guiding Principles - Part 2