5 ms·
What makes a great software engineer?
- j_baker 17y agoThere's one thing that's missing from these kinds of posts. Usually, they describe a set of characteristics of great software engineers. However, you have to be careful not to confuse that with the set of characteristics of a great programmer.
- Silhouette 17y agoYour contrast between "software engineer" in one sentence and "programmer" in the next is interesting. Did you mean to imply that there really is only one set of characteristics that define a great programmer, or were you assuming that software engineers and programmers are the same thing? (I disagree in either case, but I'm not sure how to parse your post to debate the point you intended to make.)
- j_baker 17y agoI'm using them interchangeably. :-)
- Silhouette 17y agoIn that case, let me suggest as an alternative that a common problem with these posts is that they only consider characteristics of programmers. The difference between being a mere programmer and a software engineer (at the risk of offending real engineers who earned that title) is the way the engineer runs his or her project, from capturing and interpreting the customer/client's actual requirements at the start, through to QA, deployment and beyond. Writing a program is hard, but writing the right program and being sure that it actually works is even harder, and herein lies the difference IMHO. That all said, this particular article doesn't fall into that trap, so I'll leave it there.
- Maro 17y agoDiscipline. With all due respect to the author, it's not what's described in the article: 1. Always do it the right way: Well, what's the right way? 2. Be willing to suffer: You can suffer a lot and turn out absolute crap. In fact, if you turn out absolute crap you most certainly will suffer. 3. Never stop learning: You can learn all the trendy new technologies and still be mediocre in all of them. In fact it's common for fanyboys. 4. Lend a helping hand: It's common for mediocre programmers to spread disinformation on their blogs. 5. Take your time: And you can be slow doing it! As I said, in my opinion software engineering is about discipline. You can do great stuff in any language, C/C++/Pascal/Java/Python/whatever, whether you use SVN or Git, whether you're on a Mac/Windows or Linux, but you have to be disciplined. You have to be patient enough not to start coding like a monkey and do come research before. I've known engineers who will do weeks of research before writing a single line of code, driving everyone mad, but proving themselves right afterwards. You have to be patient enough to think about your code before you write it, follow best-practices and some conventions when you write, constantly re-factor you old crap, write good comments, write Makefiles, etc. You have to be disciplined enough to do testing, have a test environment and a deploy workflow. Write proper documentation (if required), write commit messages, and so on. Engineering is not science, so you don't have to invent the wheel, it's also not art, so you don't have to be super-creative, but you have to be smart enough to be disciplined in the old-school IBM way.
- hello_moto 17y agoMy dad has no background in IT at all. He once was appointed to lead the Operation division (everything including IT). He saw that the systems his bank used was buggy and spent a few days figuring out how the systems worked (flow of the systems, input, output, users, etc). He found the problems eventually. His solution to the CEO? The IT team should be discipline in almost every step they execute. Discipline in terms of execution, discipline in terms of documentation, discipline in terms of logging information, etc. Agile, SCRUM, or whatever new methodologies out there (including CMMI) directing engineers in the software industry specifically to be more discipline. Feel free to talk bad/negatives about CMMI, but the intention is to figure out what went wrong and how to not repeat the bad experience (describe in each level). In Agile, process is not equal bureaucracy. Process is equals discipline. - Eric Ries UNIX/Linux philosophies teaches software developer to be discipline. Google has a set of coding/commit rules, rigid structures regarding their source code (code review, etc) because they knew if things were not in certain order, chaos rises.
- njharman 17y agoCommunication is important enough to have had it's own section. Communicating to future maintainers through code, comments, tests, and documentation. Communicating designs, ideas, issues with team and leaders. Communicating everything with designers, customers, testers, and stake holders. A good engineers are good individually. Great engineers work with and elevate the team(s) they are part of. In military parlance they are force multipliers.
- grayrest 17y ago> I am saying that you should try to accomplish the task on your own first, and if you get stuck, then ask for help. Don’t simply ask for help every time without first trying to solve the problem yourself. Chances are, you’ll find that you could have figured it out on your own once you know the answer. If you're a junior engineer and are working with and older engineer you respect. I highly recommend you try to solve the problem, make a start at it, and then ask your mentor what they think of your approach at lunch, on break, or at the end of the day. This gives you most of the benefit of actually implementing something while saving you most of the pain of having to maintain your mistakes.
- jrockway 17y agoYes, this is a good idea. I think you can get 90% of the way there on your own though, by asking yourself a few questions. Does it work? Am I sure it works? Will I be able to replace this code with new code in a year without touching anything else? By the time you've answered "Am I sure it works?", the answer to the next question is almost always yes. If you can test something enough to be sure it works, it's probably modular enough for your application, too.
- matwood 17y agoAlways do it the right way? What way is the right way? The right way from an engineering standpoint or a business standpoint? In my experience the right engineering way and right business way are often at odds. My boss just says I'm 'developing under protest' in these situations. :)