2 months into my job, and I have to say, it's uber-suckage. Pays ok for a job straight out of uni, but boy I never thought offices would be this god damn inefficient. It's like they on purposely don't want to give me any structured work. Half the work consists of admin type tasks and the rest is for recommending BP changes. It gets so fuzzy it drives me crazy. Shit like "Hey derf, have a look at this and let me know if we can do it like this." I'm like "Ok sure" (thinking if he explains it in such an abstract way, it should be simple.) But no. There's often no starting point. It's almost worth turning up trashed to see if it would make the day more tolerable.

Hahaha, welcome to corporate office life my friend My previous job was just like that.

The irony of the inefficient office structure is that, after a while, you can't even be arsed to try and change it and settle into it. It's hopeless anyway to expect more from your monkey colleagues than they are capable of. And because your direct superior is probably retareded too (barring perhaps if he's still young) he will only tolerate you exceeding yourself if it makes HIM look good (ie team results). Improving your personal track record will have people out to get your ass.

On the bright side: there's tons of career opportunities for backstabbers! Yay office!

lol, I guess the level of suckage depends on the job. Putting up with politics and indecision is a reality, though. Most of my job now revolves around building web applications. It'll start off with a set of criteria you need to fulfill. You make sure everyone's cool with it, you do some basic mockups and everyone says cool... then when you're about 90% done they want to change it. Like totally. To them it's just "oh yea, just move this over here and add this option".... but they're not programmers. They don't realize that "add this" and "move this" requires completely rewriting sections of code. Or hacking in the changes, which is even worse. After a couple iterations of hacking in the changes, the whole thing turns into a hack that's impossible to maintain. Plus all code is gonna have some level of bugs and the more you hack in changes the more bugs creep in. Until you're inlining javascript to update something on the client so it can AJAX in a hacked-in update to update the page with more hacked in code. Then tracking down a bug becomes almost impossible.

So yea, that's just how it is. I've come to realize that it's better going slow and rewriting the whole damned thing whenever a change happens. Hacks are bad.

„Die Komplexität beherrschen“ (take rule over the complexity) is one of basic rules whatever you build. Having look at your codes, past and current, I get feeling you do not try enough hard to make everything you do abstract, but rather to solve mostly concrete problems without leaving much room for easy mutations. Truth, you will spend more time to make an abstract thing that will solve you a task X and any other that's alike, but later you will be able to reuse that code and spare yourself lots of time and nerves.

An bad bad example for this is M$ Windows. I am pretty sure today even their best capacities do not know how exactly is the whole thing working. It just... works.

haha...I'll agree with you there. Abstracting code is difficult. I'm getting better at it, slowly but surely. Spent quite awhile recently abstracting ajax calls into a javascript class, actually...but it's probably not abstracted (or full featured) enough. Still, I hear you. It's an ongoing struggle.

Appropriate thread to notify everyone that I'm STILL looking for a damn job. I had a job interview in Frankfurt (Germany) on Tuesday, and one in Belgium yesterday. We'll see how things pan out, I s'pose.

Good luck dude. Is your CV tip-top? Remember to bend a few truths.

Heh, my CV sucks. Its pretty honest and not too honey-coated, which may be part of my problems tbh. But, in a stubborn sort of way, I feel that I should be able to get hired based on my (mad) skillz and intelligence, not my resumé. Not to mention my incredible charisma.

I don't think your job sucks as much as this though.

Bah, you pansy Ox. Drop this honesty shite. Seriously tho, one easy thing to do is exxagerate the roles you had for your previous jobs. Dont just put down the shit you did, but put down your colleagues tasks too. if you know how they did it, theres no reason why you couldn't have done it, so write it down. The interviewer will be none the wiser.

I don't really LIE, but I leave bits out to make it sound like I know more than I do. Or to cast me in a better light.

Yeah, I know I should, but I just can't bring myself to doing it. It's not that I have any qualms about it morally speaking, I'm just physically unable. Needless to say, I end up in many socially awkward situations.

Example from when I was at uni:

Girl: who do you think is pretty, of all the girls in our class? Of the guys, I think X, X, X and you are kinda handsome.
Ox: really? Cool. I like Y, Y, and Y. And maybe Y.
Girl: you don't think I'm pretty?
Ox: erh...no. sorry.
Girl: /hates Ox

I won't even bother you with how job interviews go wrong cause I refuse to go into the whole "I'm super interested in this job and will suck you cock for the rest of the year if you give it to me" routine. When someone asks me what skills you need for a given job, I'm like "Intelligence and motivation. What else would you need for any job?". Hint: they're not looking for those answers.

One can be lucky with that, till he met a master in stuff. I guess you keep mind on this, but not everyone does.

That's true. Most of the time I've been interviewed by HR type people that don't really know all that much technically. But if I'm being interviewed by someone that really knows their stuff, I'm totally honest. There's nothing that'll make you not get a job faster than being caught in a lie during an interview.

It's pretty funny...I was interviewing for a position with a server hosting facility (they host servers in huge data centers for other people) and they asked me what I rated my Linux skills at on a scale of 1 - 10. I said 4 and they were like "What? You answered almost all the questions right on our Linux test." So I guess I under-estimated by skill for that. I just don't feel like I'm that good in Linux.

Err...anyway. Ox! Wtf are you thinking with the chick thing? You've GOT to lie to chicks! If someone chick it fishing for compliments, give it to them! They might have hot friends!

OMG Satis! I agree that you probably should not tell a chick she is not hot though. Basically you would put her in the OK you are cute but not my type thing and then everyone is happy. And you are not stuck with a hanger on.

As for job interviews - being as though we seem to have gone through like 6 people trying to fill my old position with my company, I got so ticked I start asking all sorts of questions and then repeat them slightly different at the end to see if I get the same answer. Nothing else it tells me if they will remember something (such as their lies) again later. At least then I can judge if I can teach them. Blah.

And I would never say intelligence in an interview. It should be more like teamwork (which is bs - women hate each other) and willingness to find the answer. Most people care what you know but care more that you are willing to go find the damn answer yourself so I don't have to spoon feed you everything. And never show up late to a job interview. Best of luck.