Working as a programmer

Schism

I'm in college doing a general enough computer science course and I'm at the stage now where I have to choose what to specialize in as it were.

Software Development is one of those options and I was wondering if anyone in that business could give me some info about what type of work this entails.

So... What's it like to be a software developer?

p.s. I'm not sure if this should be posted here or in work and jobs

Martyr

i'm not a software developer, so maybe its not my right to comment.
not being mean, but you don't seem to be interested in software development anyway, so maybe its not something you should persue.

just sayin because you could end up getting involved in the subject, maybe spending years at it, only to realise its not really want you want to do

Schism

Average Joe wrote: »

i'm not a software developer, so maybe its not my right to comment.
not being mean, but you don't seem to be interested in software development anyway, so maybe its not something you should persue.

just sayin because you could end up getting involved in the subject, maybe spending years at it, only to realise its not really want you want to do

Sound advice and it's taken on board. Still, I'd like to hear from some people in the business.

Ginger

I work as a developer.

You need the following traits, the ability to take a lot of critism at any given time, turning market speak into technical requirements, the ability to extract information from clients to get to what they actually want.

Also you need to able to move with the times and change technologies/languages frequently and also upskill as the market progresses.

It takes a certain mindset to do it. If you dont get a buzz from solving problems which some people may think impossible then maybe software dev is not for you.

NeverSayDie

Some bits and pieces on being a software developer;

Enthusiasm and interest in the field are pretty important. Fairly obvious I guess, but it can be a reasonably demanding job, and if you're not into software development, you'd best avoid it.

One point I'd mention (that's sometimes lost on students) is that programming/coding is only a subset of what a software developer does. Things like software design/engineering, testing, technical documentation, requirements analysis, debugging, release management, technical support, etc are all in there to a greater or lesser extent too.

As Ginger points out, client-facing work also crops up sooner or later (though probably not as much at the junior end, unless you're working for yourself or for a very small company).

Working with and reading other peoples' code. This is something you'll do an awful lot of as a developer, so you better get used to it. Most software companies/depts will already have large codebases, and you'll likely spend a lot of your time working with existing code. Debugging it, fixing it, extending it, replacing it, refactoring it, etc.

Very very important; teamwork, good attitude and the ability to get along with and work closely with other people. Software is built by teams.

Generally, it's a good business to work in - the work's challenging, diverse and rewarding, and there's decent money to be made too.

Beano

if you're thinking of moving into software development you need to start developing your psychic skills now, especially if you end up doing anything that is client facing.

Schism

Thanks for the replies, they help a lot.

I'd also like to ask, would I be wrong in thinking that if I went and got a degree in Software Development this would open up doors for me in other areas of computing? for example Web Design.

Merrion

Software Engineering wouldn't be likely to lead on to web design - the latter is pretty much an arts subject these days. (Indeed most web development tools now split the design from the function)

IRLConor

NeverSayDie wrote: »

One point I'd mention (that's sometimes lost on students) is that programming/coding is only a subset of what a software developer does. Things like software design/engineering, testing, technical documentation, requirements analysis, debugging, release management, technical support, etc are all in there to a greater or lesser extent too.

+1 You'll spend a surprising amount of your day talking to people. A firm grasp of written English is a huge asset too since you'll spend a good amount of your time writing documentation, e-mails and bug reports/responses.

NeverSayDie wrote: »

Working with and reading other peoples' code. This is something you'll do an awful lot of as a developer, so you better get used to it. Most software companies/depts will already have large codebases, and you'll likely spend a lot of your time working with existing code. Debugging it, fixing it, extending it, replacing it, refactoring it, etc.

+1M

You will almost never have a blank page before you. Not just that, but often you'll have the crappiest code in the organisation in front of you. You'll rarely see the better stuff because there's much less motivation to work on it.

Schism wrote: »

I'd also like to ask, would I be wrong in thinking that if I went and got a degree in Software Development this would open up doors for me in other areas of computing? for example Web Design.

"Web design" is an awfully broad field. I've seen artists with only a passing knowledge of computers work at that and conversely I've seen coders with no idea of graphic design work at it. There are some jobs within that field which are better suited to software developers though (anyone ever see an artist try to get their head around some AJAXy Javascript?) so don't rule it out because it doesn't look like a software development job.

The one caveat I'd put in is that (in my experience anyway) the code you'll see in that field is much worse on average. If working on horrible, brain-dead code offends you then be very careful accepting a job in that industry.

Evil Phil

IRLConor wrote: »

The one caveat I'd put in is that (in my experience anyway) the code you'll see in that field is much worse on average. If working on horrible, brain-dead code offends you then be very careful accepting a job in that industry.

+1

This is an unfortunate fact of web development - designery types who are very, very good at their jobs can often be sh*t at writing code. This isn't so bad if they're aware of it and allow the devs to do their jobs. But if the old ego is inflated (They're kind of the rock-stars of the web for non-techs) they can be a nightmare to work with.

I've worked on a really good project that got delayed by months because of one designer who decided he was a coder too. All it takes is one bad apple.

Ginger

It can be a very rewarding job when everything works and all is deployed and you sit back and think I did that...

Some times it can be a nightmare, bad requirements, unbelievable deadlines and incomprehensible code.

It has its ups and downs..

I still like my job, but I am moving out of pure coding within 18 months because I dont think I can move as fast with the changes in languages.

That is one thing you will find is that, a lot of coders will leave coding after about 8 to 10 years because its so difficult to retrain that often, and also the career ladder means that to earn more they need to move into areas such as management or architecture or else be labelled as legacy programmers maintaining systems that will not be rewritten but need to be used

hussey

I work as a J2EE dev for a large bank, there is pressure as if we screw up .. well it's people's money you can imagine what would hit the fan

personally I don't think it is everyone's cup of tea, some people just 'get' it straight away and can see outside teh box, rather than a copy and paste skills I learnt in college.

Usually you tend to move away from code and more towards design/architecture as the more knowledge you build up the more you can tell other people on what you want and how etc.

working for a bank it can get stressful, but the rewards (i.e. $$) is great.

petergfiffin

It depends on what you mean by Web Design (typical SW Developer answer!!) If you mean actually doing the design work like picking pictures & the colour schemes and designing how the page should look etc then the best people I've met tend to be graphic designers/artists many of whom only have a very basic knowledge of what goes on under the covers and this definitely wouldn't require a degree in SW. If you mean writing the code that drives the website then you probably would, but I've worked with a lot of SW people who did a primary degree in subjects other than SW and moved into it.

Just on a small point, not sure how much say you have in your work experience placement but from what I've seen over my time (about 10 years in SW now) is that the type of company the person is placed with tends to be the type of company they stay with i.e. financial, SW development house, embedded etc. just something I've noticed so choose wisely!!

IRLConor

Evil Phil wrote: »

I've worked on a really good project that got delayed by months because of one designer who decided he was a coder too. All it takes is one bad apple.

In my experience it has been due to bad project management more than anything else. Managers in those kind of companies rarely come from a technical background so they're terrible at estimating the amount of time it takes to write goodworking code. Coders are bad enough at that themselves!

Ginger wrote: »

It can be a very rewarding job when everything works and all is deployed and you sit back and think I did that...

Some times it can be a nightmare, bad requirements, unbelievable deadlines and incomprehensible code.

It has its ups and downs..

The sense of achievement after completing a difficult part of a project is immense. The downside comes shortly after when the bug reports start rolling in.

The good days are when you get a straight run at some code. The time just flies by.

Ginger

Coding is not a 9 to 5 job. Some days you walk in, your finger dance on the keyboard and your code just works.. doesnt matter what you try it just works and works well.

Other days, you look at the computer, the computer looks at you, both pieces of the equation just waiting for the other part to do something.

Its hard to explain to non coders because its all about creative process, you need to the correct frame of mind, which doesnt all fit in a 9-5 time frame

seamus

Ginger wrote: »

Its hard to explain to non coders because its all about creative process, you need to the correct frame of mind, which doesnt all fit in a 9-5 time frame

Had one of them on Monday. Wrote 3 Object classes in PHP for constructing and rendering DIV-based online forms based on entries in a database in about 90 minutes. And aside from the usual simple bits (like forgotton semicolons), the thing worked exactly as I'd seen it in my head and exactly as I'd been trying to figure it out for the last 2 weeks.

I've just been poking it with a stick for the last four days wondering what else I can do with it

I wouldn't be a software dev or a web dev by any definition but I do a fair amount of coding in my job, and there's nothing better than those days where you're churning out line after line of elegant, clever and working code.

That's always offset though by those days when you just can't write even simple stuff without making a complete meal of it (and then rewriting it properly the next day).

dazberry

It can be a mixed bag, really depends if you're in a good job or not. If you work for a good employer that understands and facilities the software development process its can be the best job in the world. If you don't it can be a pretty miserable experience. Like hussey I work in a bank but in my case I wouldn't wish it on my worst enemy.

Its an experience based career, but for any job there's the right experience and the wrong experience, and if you find yourself going down the wrong track your career is pretty much going to ground to a halt. Ginger is correct when he talks about upskilling - the key is getting the right experience for your next job - unfortunately that's something that we don't get in the bank where I work - and its a shame because there are some really talented people here - and we're all stuck.

Now I know I sound really negative - simply because my career is fcuked - but it is great work - I still can't believe that people actually pay me to do this - I'd just love to do it somewhere else. If you have an interest and an aptitude for it then it is really something worth following.

D.

NeverSayDie

Schism wrote: »

Thanks for the replies, they help a lot.

I'd also like to ask, would I be wrong in thinking that if I went and got a degree in Software Development this would open up doors for me in other areas of computing? for example Web Design.

Yeah, it certainly could - several of my peers that graduated with software engineering or computer science degrees now work in web design.

Keep in mind though, as folks have pointed out above; web design is a very different skillset and area of expertise to software development. It's really a graphic designer's business; you need a good deal of artistic talent to do it any way well. I'm a pretty good developer, and as it happens I have a strong interest in HCI and user interface tech, but I wouldn't consider myself much of a designer. I can produce functional and usable web UIs pretty OK, but if I wanted something properly presentable, I'd be on the phone to a professional designer.

God knows we've all seen the results when a developer thinks they can do design work (or their manager does), and at best it leads to thoroughly mediocre UIs. Likewise, trying to get designers or HTML hackers to write non-trivial amounts of code tends to end badly too. Just because they can write code, doesn't mean they can build software.

Things like business consultancy, technical sales and marketing, etc, could also be possibilities for someone with a software background, assuming you're so inclined. (and haven't taken the direct routes in the first place).

DublinWriter

I don't want to come across as Captain Burnout here, but don't get into programming unless you really, really, really love it.

I'm 20 years in IT now, and I've seen programming as a profession go completely down the pan during that time.

Where to start with what's wrong? Well, not wanting my reply to turn something the size of War and Peace, most corporate IT shops are dysfunctional to the point of complete irrelevance.

I'm afraid that the only way to get ahead in IT these days is get a first in a Zoology degree, get hired by a big consultancy and spend the rest of your career writing nonscence client specifications and playing golf with the company partners on weekends.

Evil Phil

DublinWriter wrote: »

playing golf with the company partners on weekends.

Yep, I've worked a lot of *consultants* who took up golf to improve their career prospects.

Note to OP: I'm leaving dev work in 2 years. But 12 years of it has been good overall.

Schism

Thanks for all the replies guys, I've sort of made my decision now. Well it's made regarding software development anyway, it's not for me I think but at least now I know.

dazberry

DublinWriter wrote: »

I'm 20 years in IT now, and I've seen programming as a profession go completely down the pan during that time.

Where to start with what's wrong? Well, not wanting my reply to turn something the size of War and Peace, most corporate IT shops are dysfunctional to the point of complete irrelevance.

I for one would be interested in hearing your thoughts on this should you wish to start a new thread on the subject.

D.

conceited

Schism I think you might prefer it as a hobby, more so than a job

ElvisP

spent 14 years in all areas of IT. used to be really interesting and challenging until the managers moved in and sucked the life out of it. you now spend an inordinate amount of time in pointless meetings trying to explain the simplest concepts to morons who can't grasp the most routine.

also, you'll have to learn excel because that's the only tool the standard manager can grasp a basic knowledge of. if you want a realistic view of modern IT and its managers, read the comic strip dilbert. he nails it.

have left and am now studying in a completely different field. much happier.

those who can - do. those who can't - manage.

Schism

For those of you getting out of software development, what are you planning on doing? and for those of you who are staying put, where would you like to be?

Ginger

I am moving in Architecture and Design. I also head up our training for the team at the moment...

Currently my job is 75% coding, 25% management.. and it will move out of coding within 18 months

DublinWriter

ElvisP wrote: »

those who can - do. those who can't - manage.

Very true. I would class as completely inept 95% of the IT Managers and CIO's that I've worked for in the past 20 years and I'd cite them as living examples of that HRM phenomenon known as 'The Peter Principle'.

The reason internal IT has usually a bad rep with the business is because of incompetent IT Management/Directorship. This is turn leads to outsourcing, which is usually when the real tears start to be shed.

The reason IT Management in general is so poor is because anyone with the requisite leadership qualities climbing the greasy corporate ladder would consider the IT Department to be the kiss-of-death career-wise.

Eoin

ElvisP wrote: »

those who can - do. those who can't - manage.

That's a bit clichéd by now. Management normally requires a very different skill set than development. While I agree that many managers would not be able to do what members of their team could do, I would say that the reverse is equally true. Programmers often get tunnel vision and don't think about the myriad of other factors that a manager has to deal with. To mention an obvious one - "man management"; IT attracts a LOT of socially inept people who can be a nightmare to manage, and would never make a good manager themselves.

Personally I don't particularly want a manager who knows the technical stuff inside out, because they don't normally need to know it that well, and would probably just stick their oar in too much. Once they have good people on their team, they should be able to deal with all the other crap and trust their team's ability.

Phibsboro

Ginger wrote: »

Coding is not a 9 to 5 job. Some days you walk in, your finger dance on the keyboard and your code just works.. doesnt matter what you try it just works and works well.

Other days, you look at the computer, the computer looks at you, both pieces of the equation just waiting for the other part to do something.

Its hard to explain to non coders because its all about creative process, you need to the correct frame of mind, which doesnt all fit in a 9-5 time frame

I think that gets it exactly. I have a mate who writes books and from discussions with him it would seem coding is a very similar process. As regards going to work in it, I think if you've coded in college and looked up to find 5 hours has passed when you thought it was 15 minutes, then consider doing it as a living for a while. If that never happened I genuinely wouldn't bother, you'll get eaten by all the kids who do love it. Managing to get "flow" is important in any job but especially so in a creative one liking coding.

I came to professional coding late in my career and have had a ball doing it. One downside I find though, and I'm not sure if this is just me, is that it is *tiring* If I'm reading a new spec and trying to get my head into the different loops within loops needed to code it, I am good for nothing that evening - just mind wrecked!

C

Paul_D

I’m on the middle of my computer science degree. It's time for me to choose one of two streams: games development or embedded development. Both involve a good bit of coding which I do enjoy. What would be the best option for me? My choice is based on availability of jobs in the area, salary and career prospects only. As far as I know there are no big games development companies in Ireland so embedded development might have better prospects??

um7y1h83ge06nx

I did embedded development for Analog Devices in Limerick.

Embedded development is quite a big thing in that company, my stuff was the code for capacitative sensors on mobile phones, MP3 players etc.

Architecture used is 8051 and ARM based controllers.

Send me a PM if you have any questions.

DublinDilbert

Paul_D wrote: »

I’m on the middle of my computer science degree. It's time for me to choose one of two streams: games development or embedded development. Both involve a good bit of coding which I do enjoy. What would be the best option for me? My choice is based on availability of jobs in the area, salary and career prospects only. As far as I know there are no big games development companies in Ireland so embedded development might have better prospects??

I can't talk about Game Development but i've been working in embedded development for the past 10 years. There is some companies doing embedded development in ireland, but not a huge amount.

Its a really interesting field to be in, you need to have/gain a good understand of how many real world systems/devices work, as typically embedded devices are at the heart of pretty much every electronic product these days.

I've worked developing software to control anything from 1000A motor controllers to small embedded Ethernet devices and everything in-between.

If your interested in embedded programming make sure to develop your C programming skills, as well as the C++ & java your probably doing at college. Also get a few cheap development kits and have a mess around with them.

Also pay attention to how systems communicate (RS232,RS485,USB,TCP/IP, RF), this is massive part of embedded systems these days as typically systems will be inter-connected.

aoraki

I'd echo a lot of what Ginger said. The upskilling aspect is BIG, because it's a knowledge industry and it's changing at a fast pace.

I think to have a career with longevity, you need to be the type of person that A) enjoys the process of programming and gets a kick out of solving problems and gets a kick out of learning new stuff. If either sounds like a drag to you, then avoid.

From a financial point of view, it's not too bad. Starting out it's not great to be honest. But if you're working with in-demand technologys (.NET and J2EE are current biggies for example), if you get a few years under your belt and learn your trade you can demand a decent wage and make a good living out of it. And if you want to go work for yourself at some point, the contracting rates are pretty good too. Bear in mind though that a lot of tech firms will not pay you for overtime or weekend work (however, if you're working for a big Bank or a similar organisation, the overtime and weekend rates can be quite good).

It's a pretty flexible career. In most developed countries there is reasonable demand for developers, so it's a job that can travel well. Also, if you want to stay in Ireland and fancy a job with a bit of travel thrown in, there are US multinationals and various consulting companies that can offer that. There are development jobs with varying degrees of client facing as well.

It's a bit like a trade, there are tools to master, skills to learn. Different jobs require different tools. Over the years you pick up more tools and skills and build up your toolbox.

DublinWriter

Phibsboro wrote: »

I came to professional coding late in my career and have had a ball doing it. One downside I find though, and I'm not sure if this is just me, is that it is *tiring*

One thing is for sure and that's coding isn't a viable career-long activity. You *will* get burnt-out.

These days I think it's less and less about the code and more about knowing the framework that you're developing for, e.g. J2EE or .net.

Years ago, you'd be handcoding literally everything from scratch. These days you take advantage of the tools offered by your platform of choice.

Thankfully, most languages now are most derived from classic C, so moving from C++ to Javascript isn't as much of a leap than say moving from COBOL to FORTRAN in days of yore.

Eoin

DublinWriter wrote: »

These days I think it's less and less about the code and more about knowing the framework that you're developing for, e.g. J2EE or .net.

Years ago, you'd be handcoding literally everything from scratch. These days you take advantage of the tools offered by your platform of choice.
.

I was just thinking that the other day - when I started out doing ASP, you could spend days writing a JavaScript calendar date picker thingy and now with asp.net, it's an out of the box control that needs to be tweaked. Same with all the gridview controls, field validators etc. There's a lot more configuring than coding these days.

MOH

Watch Office Space.

I've worked with a lot of those people over the years.

Phibsboro

DublinWriter wrote: »

One thing is for sure and that's coding isn't a viable career-long activity. You *will* get burnt-out.

These days I think it's less and less about the code and more about knowing the framework that you're developing for, e.g. J2EE or .net.

Years ago, you'd be handcoding literally everything from scratch. These days you take advantage of the tools offered by your platform of choice.

Thankfully, most languages now are most derived from classic C, so moving from C++ to Javascript isn't as much of a leap than say moving from COBOL to FORTRAN in days of yore.

totally agree re the framework - for a problem solver type coder this actually makes things much more satisfying as you can get stuck into the problem. On the other hand I have know a few more techie coders get frustrated by the use of an internal framework which is common on large scale j2ee projects.

As for it being a career long activity - my experience is that there isn't really any such thing any more. Your career will move and develop as time goes on - trying to nail down something now that you think will last for the rest of your life is probably going to end in disappointment. Do something that will you get up in the morning and when you start to see the writing on the wall go do something else.

C

Eoin

For many people this is true, but if you want it, there definitely is a life long career in development - though it will probably be as a contractor. I've worked with a good few people who just spend 6 months at a time as a team lead / principle engineer on a fixed term project, and then move on. The variety of workplaces can make up for doing very similar work over and over again.

There are lots of people out there who would hate to give up getting their hands dirty and just wouldn't be happy managing other programmers.

As I alluded to earlier, management is not a natural progression from developer, as it takes a lot of other skills that you don't automatically pick up. It's not like accounting in a big 4 where you automatically move up the ranks as your experience increases.

Paul_D

Paul_D wrote: »

I’m on the middle of my computer science degree. It's time for me to choose one of two streams: games development or embedded development. Both involve a good bit of coding which I do enjoy. What would be the best option for me? My choice is based on availability of jobs in the area, salary and career prospects only. As far as I know there are no big games development companies in Ireland so embedded development might have better prospects??

so going back to my question. it seems from replies and other people I talked to that embedded systems stream would open more opportunities from me then games programming? I would really want to work for a big company like intel or alike.

Sean^DCT4

Paul_D wrote: »

so going back to my question. it seems from replies and other people I talked to that embedded systems stream would open more opportunities from me then games programming? I would really want to work for a big company like intel or alike.

Career suicide..

I started off in a large company as a junior developer and got 0 experience.
I am now in a very small development setup and see the whole software life-cycle.
The difference in experience is vast to say the least.

This is the case with most large/small development houses.

bpmurray

I disagree - in a big company you work with very experienced people and can learn a lot from them. Of course, you *MUST* ask them for help and guidance - sitting on your hands in a big company really is suicide.

I've been programming on all sorts of hardware on all sorts of Operating Systems using all sorts of languages for almost 30 years and it's been fun. I don't get to code much these days (and miss it) but the important point is that you have to enjoy looking at problems and finding a simple but elegant solution.

Go for the big companies to understand how it's done to earn money, and then work for a few years in a small company to see what it's like to frantically keep the wolf from the door, and then go back to the big one, where you'll jump into a senior role, if you've done it right.

Big companies want the clever coders, the enthusiastic entrepreneurs, the clever and ambitious people: that's what you have to aim for. Big companies also have more money, which is what it's all about, after all!

DublinWriter

bpmurray wrote: »

Big companies want the clever coders, the enthusiastic entrepreneurs, the clever and ambitious people: that's what you have to aim for.

I would disagree completely.

'Big companies' want someone who has experience in V5.2 of X, anyone with experience of V5.1 of X won't make it past the HR gatekeepers.

In-house IT in big corporates is usually the most dysfunctional department in the organisation, adopts a silo-mentality and spends most of its time policing itself and saying 'no' the requirements of the greater business.

Big-companies are bureaucracy-bound, especially in relation to IT.

Someone starting off in IT would gain far more experience in a small company than they would in a big one.

Eoin

I think that's a rather broad generalisation DublinWriter. I've worked in small/medium software companies, as well as companies with over 10,000 staff and have found positives and negatives in each.

seamus

DublinWriter wrote: »

Someone starting off in IT would gain far more experience in a small company than they would in a big one.

Actually, I would say that people are better off in a medium-sized company than a small one. You still get the benefit of being able to dip your toes into a whole pile of things, but also with the backup of a sizeable team.

In a small company with only 3 or 4 people in "IT", it can be quite stressful when you're the only person who knows how to do a number of tasks, and also there tends to be tighter constraints on budget, so you're stuck with 5/10 year old hardware until you can justify spending money on new stuff (i.e. until the old stuff breaks).

gollem_1975

DublinWriter wrote: »

I don't want to come across as Captain Burnout here, but don't get into programming unless you really, really, really love it.

I'm 20 years in IT now, and I've seen programming as a profession go completely down the pan during that time.

Where to start with what's wrong? Well, not wanting my reply to turn something the size of War and Peace, most corporate IT shops are dysfunctional to the point of complete irrelevance.

I'm afraid that the only way to get ahead in IT these days is get a first in a Zoology degree, get hired by a big consultancy and spend the rest of your career writing nonscence client specifications and playing golf with the company partners on weekends.

where can I subscribe to your newsletter ?

Am reading a book called "my job went to india : 52 ways to save your job" by Chad Fowler at the moment.

I wish I had read it a couple of years earlier.

I think it gives a realistic perspective on the industry at the moment and gives some advice valuable for people currently working and those aspiring to work in the Software Industry.

the aforementioned book refers to another book called The Pragmatic Programmer ( which I haven't got around to reading it yet .. but I have time on my hands now )

perhaps the OP might want to read either of these titles ? has anyone else read them and if so what are your opinions ?

IRLConor

gollem_1975 wrote: »

the aforementioned book refers to another book called The Pragmatic Programmer ( which I haven't got around to reading it yet .. but I have time on my hands now )

perhaps the OP might want to read either of these titles ? has anyone else read them and if so what are your opinions ?

The Pragmatic Programmer is excellent. Loads of great advice and very digestible.

A couple of times I've felt down about coding I've (re-)read that and/or Jon Bentley's "Programming Pearls" to remind me of some of the stuff I love about programming.

dazberry

I find those books really frustrating and I have read a lot of them - some repeatedly, from The Mythical Man-Month to Cockburns Agile Software Development. Truely brilliant and IMO every serious developer should read them. Why do they frustrate me? Because if you work in a sh1thole - there are no happy endings. All those crazy examples from Acme ABC that sound so ridiculous on paper are where you work. Dilbert's pointy headed boss has nothing on your overlord. All those really simple things that could make life so simple for everyone - are apparently against company policy, and sure lets put all the developers in an open plan office with the sales staff - because chaos and noise are good - and no headphones. I feel an idea for a book coming on

D.

DublinWriter

dazberry wrote: »

Dilbert's pointy headed boss has nothing on your overlord.

Client: We want a web-based application
Me: Ok, how about we develop it in c# .net
Client: But it's company policy to use Microsoft technologies
Me: c# is a Microsoft Technology
Client: Oh, ok, can't we use VB instead? All our existing systems are written in VB
Me: Ok, you're the boss, VB and ASP.net it is
Client: ASP? Can't we just use VB? We can only use Microsoft technologies.

I kid you not. This from someone on a salary of nearly €100k pa.

...and before you ask, the individual's people-management and project-management skills were even worse than their technical knowledge.

Most of the time working in the I.T. sector is like 'Night of the Living Numpties'. As a consultant, it's always a pure-joy for me to work directly with end-users because at least they know what they want, but it's a tough political balancing-act to do this and play ball with internal I.T. departments at the same time.