Irrespective of the language programmers choose for expressing solutions, their wants and needs are similar. They need to be productive and efficient, with technologies that do not get in the way but rather help them produce high-quality software. In this article, we share our top ten list of programmers’ common wants and needs.
word !
Ease of deployment is one of my biggest pet peeves. Does the user have to download some massive runtime or other assorted libraries for the language/framework I’m working in.
I would’ve guessed that at least some mention to things that are not technical would’ve been present. I mean things like “Decisions based on politics instead of technical merit” or “Planning based on how much you can squeeze your employees instead of on how long it really takes to do something” or even “Having to go into management roles to get an adequate raise”.
I don’t know but for many developers I know the technical stuff is more or less covered, but it’s these kinds of things that get to their nerves on a day to day basis.
if they were talking about in general, not re: web programming, i’d say osx is just about there for most of their pet peeves list and wants/needs. i’m consistently surprised at how well the development of this thing is going…
Now !
I don’t know about you guys, but all I want is a good work environment [not coding-wise but physically], flexible working hours, nice people to work with, fair salary and a management that’s a _bit_ smarter than a bullfrog’s arse. All other things [including some of those mentioned on the article’s list] are less important. /* For me. */
not.
i think programmers want a life. and that is dependent on things other than code libraries, tools, etc.
We were having this discussion at work recently and concluded we actually want frameworks and libraries that do far more while requiring far less from the programmer. Existing libraries seem to work on the all-or-nothing approach – they can do all the work or they can give you all the control. Very few get the balance that would let us write just the bits we were interested in.
A lot of the time this can also be summarised as “lack of sensible defaults”.
I would’ve guessed that at least some mention to things that are not technical would’ve been present. I mean things like “Decisions based on politics instead of technical merit” or “Planning based on how much you can squeeze your employees instead of on how long it really takes to do something” or even “Having to go into management roles to get an adequate raise”.
I don’t know but for many developers I know the technical stuff is more or less covered, but it’s these kinds of things that get to their nerves on a day to day basis
Welcome to the world dominated by the market economy.
1. Lists that begin and end with vi and gmake.
2. Lists that swim in so many buzzwords and repeat themselves so many times to get to a magic number (“10”) that they wind up saying very little.
This one actually makes a fair amount of sense, cut down about 50%. My bottom line would be tools that aren’t just designed to showcase features and don’t take months to learn and constant practice to stay good with. I’d rather rewrite STL w/ CodeWarrior than use it w/ Visual Studio.
Natively compiled Python. That’s what we want!
Isn’t there a Python2C++ somewhere? Then you could have the natively compiled python code
It’s hardly the same thing.