nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Child Item

What did you suck at or hate?

Nulty

I'm interested to know what you professional developers found most difficult, hated or just struggled with most when you were at college getting your qualifications. I think it would be great inspiration for anyone trying to get through college knowing about some of the things that mildly (;)) successful IT professionals and developers had to deal with during their education. I'm sure everyone in the industry has their strong and weak points - what are yours?

I imagine maths will be in high representation, databases for some.

I still find it hard to get my head around the OSI model personally, I mean what is actually going on there!? I was never taught algorithms properly but it is bugging me so I'm going to have to scratch that itch myself.

What about you?

Find more posts tagged with

Quick Links

Comments

Encrypted Pigeon

Not qualified yet, but it has to be database theory, I would sooner scratch my eyes out than sit through that again. Yes I know its important, but damn!

k.p.h

Sintel wrote: »

Not qualified yet, but it has to be database theory, I would sooner scratch my eyes out than sit through that again. Yes I know its important, but damn!

Fook me, Databases ..! Mind numbing horrendous experience.! Delivered in monotone by a guys who's idea of fun was a discussion about serializability..

Top DBA's get paid a huge amount though so I'm sure swimming in a sea of loot takes the boredom away..

Aswerty

I didn't do computer science in college but I found hating or liking a subject was hugely affected by the quality/personality of the lecturer and how they presented the material. You can have lecturers who go into class and read from a previous lecturers set of notes for an entire module and then you can have lecturers who do their own notes that are updated each year and they teach as opposed to lecture.

komodosp

Took me years to get my head around classes! Granted I was working in COBOL for most of those years, but "dabbling" in C++, but I missed the first lecture talking about classes, and didn't catch up until ages later.

For some reason it was always explained as an analogy to a stool (e.g. a stool is an object, you can have a stool with 3 or 4 legs, and the legs are objects too, or a new type of stool with a back, etc. etc. to explain extending classes) but I never really saw how that compared to actual computer programming....

Creamy Goodness

ie6 development and maintenance.

[Deleted User]

Databases, but then you see they are literally everywhere so you have to suck it up and get used to them in some way at least.

Maths, but I have avoided it through the choices I have made so I don't often come in contact with it (specifically).

CrazyFish

Parts about compiler construction

Odaise Gaelach

I've no clue about how electricity works.

Sparks

Sintel wrote: »

Not qualified yet, but it has to be database theory, I would sooner scratch my eyes out than sit through that again. Yes I know its important, but damn!

Funnily enough, I didn't take that course, thinking that it was irrelevant and I could pick up whatever I needed from a SQL handbook. Now I write database kernel code for a living*. Wish I'd taken the course...

...and actually, that about covers most of my thoughts on this one - you can't tell in college what you'll need and what you won't use, and you shouldn't try because where you go in the next forty years can't be predicted well. Learn as much as you can, at as fundamental a level as you can, and learn it well. The rest will take care of itself.

I would add two specific points though, which I don't see mentioned enough when this kind of thing is discussed:

Learn decent written and spoken English. It's not a case of "stupid foreigners, with their stupid foreign languages" - English is the lingua fraca of our industry. Sixty or seventy years ago, if our industry had been around, it's lingua fraca would have been German. Fifty years before that, French. Before that, Latin. Today, it's English, tomorrow it might be Mandarin or Hindi, but for now, it's English. And frankly, half the Irish developers I've known aren't that great with it and could benefit from some time spent improving their linguistic ability.
Learn people. Seriously, **** that stereotype about how developers are all nerds and geeks who fear and shun society to the point where Aspergers is referred to by some as the engineer's disease. It's not accurate, and we should be actively fighting it. Programmers, arguably more than any almost other profession, need to have good social skills.

Look, if you're working solo on a small project, you can afford to be insular and acerbic. But 90% or more of the programming jobs out there are not like that; you have to deal with customers, managers and other developers. If you put a handful of developers into a room to work on the same project and they have lousy social skills, you'll wind up with the loudest bully saying they run everything, and everyone else will probably quit working on the project (and some will actually quit the job ). We're an industry where we produce things that we conjure up in our imaginations using hard-earned skills; doing that as part of a team is a pretty tough social skills challange because you have skin in the game and your mortgage is riding on the outcome.

So figure out a way to keep your ego in check (or at least, learn to keep an eye on it and know when it's getting a bit much). Learn to listen to others -- and believe me, that's a rare skill; far too many of the people in our industry operate on the transmit-only model, where "listening" means "pausing to catch your breath for the next statement". Entire teams have quit from companies I've worked at (hell, I've quit with them) because the company hires one person like that who makes the lives of the other developers difficult (and you'd think companies would learn, because that's an expensive thing to go wrong).

Oh, and for the list, I still have problems with ordinary differential equations, I never really clicked with them.

*well, not really, I'm doing networking code in the high availability and disaster recovery part, but it's less funny when you include that bit.

satchmo

Statistics. Ugh.

At one stage, even our statistics lecturer said "Look I know this stuff is boring, but let's just get through it, ok?"

Colonel Panic

The people skills are the hardest. Learning when to shut up. Learning to straddle the line between mythical "best practices" and the commercial reality of writing code on a deadline for customers who don't give a hoot about TDD or Agile. Accepting that while your senior colleague might not not as much tech stuff as you, they have years more experience.

The technical stuff is easy. For a long time, I sucked at all of the above. It's only now I've got people who are junior to me that I get it. Now I'm cringing in hindsight at some of the stuff I said.

arleitiss

my main problem is design, I just can't come up with good design/template, otherwise I know how to code it, use php, use databases, JS, css etc.. So I started learning the theory of colors and typography, helps a lot.

Dboy85

I struggle daily not to brutalise condescending colleagues. I'm not talking about senior figures in the work place but busy little cnuts on the same pay grade with the same responsibility, that haven't got half the experience of peers, but still believe they are top dog.

Only the fear of incarceration stops me from snatching the life right out of them.

/rant

That and design...boring as hell mulling over pixel dimensions. Back end ftw...giggidy

starlit

Didn't like or wasn't great at Java, VBA, Circuit/logic design, but wasn't too bad at De Morgans Theorems once I got to grips with it, took a while to get my head around it but didn't like it all that much.

Touched on a bit of python and didn't like it much. Actionscript was ok but a bit frustrating to learn the code preferred the multimedia design aspect than the coding of it when didn't have enough resources at the time while in college compared to other programming languages. Good at most other programming languages in particular best at web programming (loved HTML CSS and PHP) and good at os programming languages like Unix not too bad with windows programming but very basic stuff.

Ok with ASP.net/.net stuff better at VB than that but only when creating websites, creating a database from scratch using code was a bit difficult for me as code often didn't work for me. Good to spot mistakes if using a good application to create the code like Notepad++ is a lot easier to use than notepad.

Generally good at SQL depending on what application I am using if its access/excel was a nightmare for me sometimes but when using MYSQL or PUTTY was a lot easier to code SQL, loved databases. Otherwise Decision Support Systems was my biggest pet hate! Ugh!

Some aspects of Networking was difficult for me the theory I could get my head around no problem but the some of the practical elements I found hard but did ok in them. Did well in some aspects did only alright in others.

Did business maths/statistics not a major fan of maths but did well in the subject otherwise. Haven't done anything in the area of application development like android or anything like that.

Have yet to brush up on a few other programming languages I've yet to learn Javascript, C# and Ajax when Java wouldn't been my best language while the rest I wasn't bad at them.

I was good at multimedia, enjoyed it but some aspects was hard in college but otherwise ok, great to come up with ideas but tended to run away with my ideas and sell myself short when it came to the final project. Though when it came to web design I was very good at it.

Loved any other part of IT I studied in college. Not in any particular job at the moment though so really only starting out my career yet.

starlit

Aswerty wrote: »

I didn't do computer science in college but I found hating or liking a subject was hugely affected by the quality/personality of the lecturer and how they presented the material. You can have lecturers who go into class and read from a previous lecturers set of notes for an entire module and then you can have lecturers who do their own notes that are updated each year and they teach as opposed to lecture.

I very much agree on this. I suppose every lecturer is different depending what subject they are lecturing in. Some modules are harder to lecture on than others a lot of it learning for yourself a lot of the time. Like programming you either pick it up or don't but everyone is different some are better at some programming languages more than others. A lot of it is down to aptitude and interest I suppose.

I found that too while I were in college I didn't do a computer science degree but did a postgrad in it alright.

RedXIV

Two aspects which came to mind immediately were pointers in code - I literally spent a year beside mates in college going "seriously....the hell would you use one of these for?!"

And then there was data structures where I'm pretty sure I missed a class or something in college because it wasn't until about 3 years later looking at a microsoft exam when it all clicked into place. one of those real

moments

starlit

RedXIV wrote: »

Two aspects which came to mind immediately were pointers in code - I literally spent a year beside mates in college going "seriously....the hell would you use one of these for?!"

And then there was data structures where I'm pretty sure I missed a class or something in college because it wasn't until about 3 years later looking at a microsoft exam when it all clicked into place. one of those real moments

Its a great feeling when it all clicks and works together! Happens for some sometimes does not always happen! Good going though.

CreepingDeath

I hated maths in college.
Since the course was skewed towards science there was a lot of calculus, rewriting formulae, etc.
None of which I've ever needed in standard commercial software development.

There was an optional graphics course which was much more practical, matrix and vector operations, transformations etc.
Much more usable and practical math.

However in the real world, if a company needs someone with maths skills they hire them specifically.
So you might have one math nerd with some programming skills and the rest are standard developers.

G-Money

I'm horrendous at mathematics, always have been.

When I did my HNC, I struggled with Databases and some stuff around low level binary code.

Thankfully I haven't had to use any of it since really.

Rossin

java- sucked the life out of me in college, ended up moving course!

starlit

Sometimes I wonder why you even need maths for a computer science course? You can get away with ordinary level maths for it and could avoid it if you wanted and just do a language in it. Its the case in UCC and some colleges you can avoid maths and do a language or you must do Maths depends on the course, department and the college.

Java can be a love or hate kind of programming language!

CreepingDeath

Rossin wrote: »

java- sucked the life out of me in college, ended up moving course!

If Java was your first introduction into object oriented programming then it might be overwhelming.
But it's certainly easier to learn than C++.

starlit

CreepingDeath wrote: »

If Java was your first introduction into object oriented programming then it might be overwhelming.
But it's certainly easier to learn than C++.

I found Java difficult to get to grips with, how is C++ or C# any different? Which of the three be easier to learn?

Though the principles are similar they are still different programming languages and procedures.

Skrynesaver

doovdela wrote: »

Sometimes I wonder why you even need maths for a computer science course? You can get away with ordinary level maths for it and could avoid it if you wanted and just do a language in it. Its the case in UCC and some colleges you can avoid maths and do a language or you must do Maths depends on the course, department and the college.

So how do you size a platform for your code without Big O notation etc...

starlit

Skrynesaver wrote: »

So how do you size a platform for your code without Big O notation etc...

ah!

Rossin

CreepingDeath wrote: »

If Java was your first introduction into object oriented programming then it might be overwhelming.
But it's certainly easier to learn than C++.

I moved to a apps & support degree and I'm now a network administrator so I've never looked back, hated it! It was down to an awful lecturer as well though, the whole class never got to grips with it because they never learned the basics properly. Sitting their finals most of them were still clueless (almost all passed mind you which shows how good some of our graduate soft dev/eng are

)

Sparks

RedXIV wrote: »

Two aspects which came to mind immediately were pointers in code - I literally spent a year beside mates in college going "seriously....the hell would you use one of these for?!"

See, that's why you shouldn't try to pick what you should and shouldn't learn in college while still in college

starlit

Sparks wrote: »

See, that's why you shouldn't try to pick what you should and shouldn't learn in college while still in college

Sparks

doovdela wrote: »

?

Because pointers are probably one of the most important features in code. If you don't know pointers, forget ever getting a job working with C or C++ until you do; and those are the two most popular languages in the industry as a whole at the moment, and there's little sign of that changing. And while languages try to wrap them and hide them away, the thing is that if you don't understand pointers, you'll never really understand half the data structures we use, or the language features people are trying to use to replace pointers.

starlit

Sparks wrote: »

Because pointers are probably one of the most important features in code. If you don't know pointers, forget ever getting a job working with C or C++ until you do; and those are the two most popular languages in the industry as a whole at the moment, and there's little sign of that changing. And while languages try to wrap them and hide them away, the thing is that if you don't understand pointers, you'll never really understand half the data structures we use, or the language features people are trying to use to replace pointers.

I am a little lost as to what pointers are as I have never learnt C and C++ and hope to learn sometime in the future!? I've learnt Java.

Really, I thought there might be a chance it change hope there is, there seems to be a big thing in the web programming and mobile programming industry at the moment? I would hope to follow on one of those areas rather than Java or C codes despite C coding family seem to be requirements for most job specs.

I understand so Pointers are very important for those languages.