Forget what everyone is telling you.. Work harder? Seriously? M8, I dont think you're a whiner. Your young and trying to make choices now that effect the rest of your life. The same thing software developers do everyday while they are writing their code. Work harder. Don't bother. Degree? Who cares. Grab the next copy of the rich list for whatever country you are in. Go through the top 20, top 100. Then list how many of those people have degrees, how many of them have worked hard.. Then list how many people dont have degrees and havent worked hard but have been smart enough to take advantage of the work of others. I think you will find list 2 bigger than list 1. At the end of the day, you have to decide whats important to you. What floats your boat? What is your measure of success? Money? Family? Pride? If you want a job in Seattle, take the risk, save the money and go. Without risk there is no reward. Am I a troll? lol.. Probably. I'm a software developer with some free trolling time on my hands. I have not finished high school, I dont have a degree. I have been developing for some years. I never worked hard and now as a result of having never worked hard, I have been rewarded well and dont have to work at all, so I code when i feel like it and troll in between. I was watching the 3 amigos when I was a kid (i hear you say, what is he crapping on about now).. The Mexican (i think he was Mexican, no offence intended) guy says, "if you want the woman, you just take the woman". I wouldn't suggest you go picking out the women you want and taking them, but apply that to the rest of your life. If you want it, take it.. nobody is going to hand it to you. Forget the guarantees, there are none in life. Grab hold of ya nuts and get out there.. If you fall down, who cares, we all do.. Get up and go again.. Dont live in your head wondering what if... just do it. Troll rant over..

In my experience, if your asked to do such a thing, you should just pretend to do it. Anyone in charge of any production system would in return for your efforts tell you that your code isn't going to be released due to risk. If its just everyday coding to be released in the future, it wasn't that important to have it done over night. If you putting together a prototype or demo for a client to be used the next day then I would avoid this too. The client should be shown more respect and when everything breaks your left embarrassed. If your in a situation where you must do coding and release or life as we know it will end for your production system, ask yourself why this is the case. Is it because an overnight fix was done 3 months before and wasn't tested properly and causing issues now? Probably.

A good man? A Buddhist? Personally, I've never met or really even heard of a Buddhist or a good man making products in slave labour factories.

Think about the source of the behaviour. It might not be what you think. The behaviour creates a symptom that makes it appear as though they are simply being difficult and own their own path. However, generally passive aggressive behaviour comes from a lack of self confidence and insecurities. They probably were not socialised properly as puppies.. lol The person may not have the skills for the social manners required for group discussions or know how to get their ideas across to others in a way they are understood, which would create frustration for themselves which turns into inpatients and a behaviour that is somewhat antisocial, which of course is where the problem started. The question is, do you tolerate it or try to work with the person in a way that will give you the best result. To approach it with a normal management style of, this is what I expect from you, this is what you must give to the team will probably just leave them in a situation where they feel more insecure and more of an outcast which is why approaching it that way would make it seem like the passive aggressive has simply turned to aggressive. This behaviour is very common in the world of software development. How many of you NON IT friends care about your technical ramblings? Try talking software development to them and see how quickly they run.. haha What do I base these things on. 1. At one stage at a previous employer, relationships got so bad that we got to experience classes in personality, behaviour and conflict resolution. 2. My sister is a qualified in this field, also has an business IT degree. Our father was a programmer, I am a programmer and she did a degree in IT while still working out what she really wanted to do. Ask her and us IT people all have borderline personality disorders. (generalising of course)

I'm with you! Well partly. My father was a developer with his own business (we employed 300+ people) I began there writing Clipper code in the 90's. I have since moved through the world of delphi, vb, .net and the like. I have worked with traditional style, sequential non event driven code , to COM+, and so on. The project I currently work on is OO based. My preference has become somewhere in the middle. I appreciate OO however also recognise that the end result is a system that does not perform well with large sets of data. Maintenance can be a nightmare. One example is the need for a new method parameter. By the time you have updated your interface, moved through all your inheritance chains and service layers, you have modified (in my case) about 20 files. You end up so far removed from where you started that its painful. In the end, all that was needed was a True or False to be passed to a method. There is the hack way of doing things and there is a purist way, but somewhere in between is "commercial reality". As for n-tier, I do believe there is benefit in separating the layers. One of those benefits is security related. If your transactional layer is segregated for example, it can exist on a server other than your web server and separate from your database server. This of course allows operations to sit behind fire walls, access controlled via authentication and restrictions on IP address. You may get to our web server but to make it to the database is quite unlikely. You will find no connection strings or the like at the web level to help you. My gripe, because I feel like adding to yours :) is reflection. Used well, it is powerful and very useful. However when you use it to start invoking code, late bound, you again create a maintenance nightmare. To give an example. I came across a method that iterates through some xml nodes. The end result, nothing.. why, because it doesnt provide one.. I think it was there just to keep the cpu warm. Now dare I remove it???? NO!. Sure, I can removed the code that does nothing, but I can not removed the method. It may or may not be called by reflection and if it is, how can you tell? Your concious developers who take the time to clean up as they go, remove old code and the like now wont do it. Who wants to be the one that does a reference search finds that a method is not referenced, then remove it, only to find out that everything falls over in 6 months time when you run one of those bi-yearly type financial functions? After sitti

Funny stuff. Database related code should remain with the database. Just because in your experiences people don't seem to be able to write good clean sql code doesn't mean its to be avoided. Before a proc is committed to source control or production it should be reviewed just like you should with other code you write. Instead of complaining and avoiding the real world, offer your expertise to help others, offer your time to review and explain the hows and whys of your criticisms. Don't let the end product suffer just because some are not as capable as yourself. Make the best choice of technologies to use, decide on the best way to use them, educate yourselves and your peers.

Sounds like somebody has failed to properly manage projects and resources. At the start of every financial year and with every new project you know what resources you have and the term you have them for, try planning to use them properly.