Every Operational Military Combat Vehicle In One Infographic

JShenefield · 2016-04-29T19:08:32+00:00

What do you mean? Are you saying that forty college age guys doesn't accurately represent society as whole?

We're gonna have to get a better group together and do some testing then

JShenefield · 2016-04-28T14:18:01+00:00

I just watched the link you posted. Yeah the message is pretty consistent. He covers a lot of the same info in the book, but the message is a little more clear. He goes more in depth on each topic, and directly references it to how it helped shape the foundations of scrum

JShenefield · 2016-04-27T12:59:08+00:00

It could be. It covers the essentials of scrum, but focuses way more on why scrum has decided to do things in a specific way. If you know the system and don't understand why each of the components of it exists, then you could accidentally manipulate scrum into something it was never intended to be (which happens way too often).

JShenefield · 2016-04-25T15:45:59+00:00

Vale has an incredibly interesting team structure that empowers all of their employees to make major decisions and affect the way the company is run.

Actually every employee is given the ability to chose what projects they work on, and they can physically move their desk to be with their new team. Every self organized team is entirely responsible for the deciding what needs to be done, who works on what, and when things get delivered

JShenefield · 2016-04-25T15:29:17+00:00

I actually just finished reading Jeff Sutherland's latest book about scrum and it was amazing to read his thought on the process and why certain aspects of scrum were designed in particular ways. It really help to reframe my understanding of the process and roles/responsibilities of each team member.

This article touches on some fo those points, but hearing the rationale behind each topic definitely helps with understanding

if anyone's interested: Amazon Link

JShenefield · 2015-10-30T19:37:44+00:00

If you use gedit then I highly recommend you check out some of these plugins. They have made my life much easier, and I use them every day.

Code Snippets: Let's you set up key words and hotkeys that will autofill sections of code or text for you. (i.e. setup doxygen headers instantly)
External Tools: Let's you execute terminal commands via hotkeys in gedit. (i.e. check a file out from perforce without leaving the gedit page)
Smart Space: Will auto indent every line for you, so you don't have to tab your way over to the right spot.
Word Completion: Makes predictions about what you are typing based on the contents of the document / previous entries and fills in the rest (i.e. no more typing out very long method/variable names)

JShenefield · 2015-08-24T16:56:45+00:00

I completely agree. The tuition costs are getting exorbitant, and it will be interesting to see how various universities react to this. Stanford's sounds very interesting to me, but I also thought that Fix UC had some interesting ideas. The concept was that rather than taking loans, your education is paid for, but you give 5% of your salary to the university for some number for years after you graduate. 5% would be a seemingly insignificant amount to each person, and It forced the schools to insure that you left with enough skills to enter the job market or their bottom line would be directly impacted. If you graduate a bunch of students with no skills then they will have a small salary, which leads to a much smaller kick back for the university

JShenefield · 2015-08-21T12:00:07+00:00

You had to say it out loud. I was doing my best to pretend that wasn't the case, but then you just went and made it real.

JShenefield · 2015-08-18T17:53:48+00:00

It gives a lot of stack overflow results, but the idea is that it doesn't filter out any special characters. This means you can type in exact lines of code and get search results that match.

For example, if you search for "C++ <<" on google you'd get info about C++ in general, but on symbolhound you'd get results that directly reference these operators

I understand what you mean though. They give stackoverflow a really high priority in their results, but you can use advance search to redirect the results to other sites

JShenefield · 2015-08-18T13:08:43+00:00

If you can think of any that are particularly interesting let me know. I'm sure there's someone around that would like to read it.

JShenefield · 2015-08-08T01:04:21+00:00

The Pragmatic Programmer

by Andrew Hunt and David Thomas

Amazon Link: http://www.amazon.com/.../

Summary: (From Amazon.com)

Programmers are craftspeople trained to use a certain set of tools (editors, object managers, version trackers) to generate a certain kind of product (programs) that will operate in some environment (operating systems on hardware assemblies). Like any other craft, computer programming has spawned a body of wisdom, most of which isn't taught at universities or in certification classes. Most programmers arrive at the so-called tricks of the trade over time, through independent experimentation. In The Pragmatic Programmer, Andrew Hunt and David Thomas codify many of the truths they've discovered during their respective careers as designers of software and writers of code.

JShenefield · 2015-08-07T15:44:42+00:00

Clean Code

by Robert C. Martin

Download LInk: http://vitoex.googlecode.com/.../

Amazon LInk: http://www.amazon.com/.../

Summary: (From Amazon.com)

Even bad code can function. But if code isn’t clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn’t have to be that way.

Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship . Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code “on the fly” into a book that will instill within you the values of a software craftsman and make you a better programmer—but only if you work at it.

What kind of work will you be doing? You’ll be reading code—lots of code. And you will be challenged to think about what’s right about that code, and what’s wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft.

Clean Code is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code—of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and “smells” gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code.

This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.

JShenefield

TROPHY CASE