Click here to Skip to main content

The Insider News

   

The Insider News is for breaking IT and Software development news. Post your news, your alerts and your inside scoops. This is an IT news-only forum - all off-topic, non-news posts will be removed. If you wish to ask a programming question please post it here.

Get The Daily Insider direct to your mailbox every day. Subscribe now!

 
You must Sign In to use this message board.
Search this forum  
    Spacing  Noise  Layout  Per page   
News10 enemies of being a good programmerstaffTerrence Dorsey3 Jan '13 - 10:10 
So, what makes a good programmer? This is debatable point and to make things simpler, let’s see this the other way round i.e. discuss the top 10 enemies which can prevent oneself from becoming a good programmer.
Pro tip: don't do these things.
GeneralRe: 10 enemies of being a good programmermemberlewax003 Jan '13 - 10:55 
11. The Lounge
GeneralRe: 10 enemies of being a good programmermemberdevvvy3 Jan '13 - 15:57 
"Not being latest" --> bs
dev

GeneralRe: 10 enemies of being a good programmeradminChris Maunder3 Jan '13 - 17:45 
Absolutely. I would say "blindly following the latest" is a huge timesuck and can totally derail a project.
 
Software is meant to serve a purpose. It's rarely there to be a thing unto itself. It seems more and more devs are forgetting this and focussing on the code and tech rather than what they are trying to actually provide for users.
cheers,
Chris Maunder
 
The Code Project | Co-founder
Microsoft C++ MVP

GeneralRe: 10 enemies of being a good programmermemberdevvvy5 Jan '13 - 14:25 
riding on .NET 1.0 success Microsoft has spent last few years embarked on changing the programming "Paradigm" (WCF/WPF/SL) - reinventing framework which performs nothing more than what Winform/Socket already accomplished, while in the meantime missed out entirely on the mobile market.
 
Those who busy themselves learning WCF/WPF will find themselves all of a sudden now needing to program yet-another-new-API "WinRT"
dev

GeneralRe: 10 enemies of being a good programmermemberPhat (Phillip) H. VU3 Jan '13 - 16:16 
"Not estimating (or planning) the work or tasks". Wink | ;)
 
Working without planning will lead to failure.
GeneralWhere's "Not knowing how to code?"adminChris Maunder3 Jan '13 - 17:53 
This all seems a little pithy. Where are:
 
1. Not knowing how to actually architect and code. Maybe a little obvious but I think we've all seen code that shows the dev just doesn't get it.
 
2. Not knowing how to write good code. He mentioned Agile practices (which I will not get into a debate on here), but not SOLID. Poor Uncle Bob!
 
3. Not testing. No unit tests, integration tests, performance tests.
 
4. Not understanding what the software you're writing is actually meant to do. This, to me, is the 2nd biggest reason a dev is a bad dev (after #1: Being a bad dev). Once you understand programming it's a doddle, but being a good programmer means understanding what the app actually is meant to do (not what it does) which enables you to make decisions that focus on the app's experience, not on what makes you, the dev, happy that day.
 
Ugh. I could go on. (though I already have, I guess...)
cheers,
Chris Maunder
 
The Code Project | Co-founder
Microsoft C++ MVP

GeneralRe: Where's "Not knowing how to code?"memberZac Greve5 Jan '13 - 3:11 
Maybe someone here should write an article on that. That article (or series) would get my ((5!)!) (= 6.6895029134491270575881180540904e+198)

Bob Dole
The internet is a great way to get on the net.

D'Oh! | :doh: 2.0.82.7292 SP6a

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   


Advertise | Privacy | Mobile
Web03 | 2.6.130523.1 | Last Updated 25 May 2013
Copyright © CodeProject, 1999-2013
All Rights Reserved. Terms of Use
Layout: fixed | fluid