Incorrect. You may have alzheimers or take a blow to the head and forget your destination after embarking. Or you may be Forest Gump and just decide to run one day for no reason.

Prepare yourself for more burning tomorrow.

Incoherent argument. What was the point? I've read a few of this person's posts and after reading them I'm always left with the feeling that they must be terrible to work with.

Maybe it was a test to see how you would respond to a superior or colleague upon being given incorrect technical spec and/or guidance!! ;)

tumbledDown2earth wrote:

Gawd I just dont understand how such people get into mainstream interviewing in super large MNCs.

Well the really technically inept sociopathic ones usually get there by being persuasive. They are good at charming or bullying colleagues and superiors into accepting that they know what they are talking about.

Roger Wright wrote:

but the odds of someone my age landing one of them are fairly slim

Don't think like this. This coupled with some bitterness towards your employers or job can spiral into "I hate my job but can't leave". Been there before and its a bad place to be. I'd clean the desk (which is a very odd condition for a raise), take the money and start looking for a new job. If your boss is willing to throw around +10% over a dirty desk and you're a valued employee with other employment options then I think you have the upper hand and can squeeze your boss for whatever you want.

:wtf: Starting to wish I had but I'm too poor.

Looks similar to the algorithm for insanity:

while(unexpectedResult)
{
repeat();

if(insane) break;
}

I am writing some software for a client and find some of their business processes and way of doing things a bit illogical and confusing. A number of times I have thought "Why do they do it that way, wouldn't it be simpler to do it this way instead. Plus it would make my life easier too". On the occasions I have brought this up, I am usually met with the reply "that's the way we do it". Anyone else get this much? Do you persist and argue your point or just give them exactly what they ask for? It's not my place to change their business processes, so I'm inclined to give them what they want and take the money. However, I'm left with the feeling that the application was not as good as it could have been.

Went into a busy UK corner store one morning looking to buy a lottery ticket or "lucky dip" as it's called when the numbers are autopicked. Bloke behind counter: "What can I get you, pal?". Me: "Five lucky dicks, please". :~

Just a glitch in the matrix :suss:

I like your definition. In a text I read on buddhist meditation, from memory, the author described 3 aspects of consciousness. Your's closely aligns with the third. 1. An aspect where you just "be", where the mind is clear, and you just exist in that moment totally absorbed by a task. eg meditation. 2. An aspect where you think about and are aware of the present moment, watch, feel, smell etc and comment on your existence in realtime. eg thinking I'm walking some stairs, these stairs are steep. 3. An aspect where you are able to reflect on your current or previous thoughts. eg I know I am/was thinking these stairs are steep.

This may give a snapshot of the mind at a certain point in time but I think consciousness goes well beyond this.

Don't know how old your Dell is, but I have an 2 year old Inspiron in which the motherboard recently died. I was really pissed off and I only had the standard 1 year Dell warranty, so it was 1 year out of warranty. I called Dell expecting to get nowhere with the call centre operator, and was ready to get all shouty and aggressive. However, the Dell employee on the phone fell over himself to help me and offered several options to get the laptop up and running at no cost. I ended up getting a new motherboard couriered to me, popped it in, sent the old one back and the laptop is as good as new. All for free! We'll see how long this one lasts, I have noticed a decline in quality over the last couple of years. The first Dells I bought are still running after 12 years or so. I was pretty impressed with the way they handled my complaint though.

Yeah, definitely finding I get caught up too much in the larger scope of the application. I'll think of a nice way to encapsulate some functionality in class A and then think of how that links with Class B and so on and so on until my brain shuts down with despair from trying to juggle this mental object graph and the realisation of all the other features I still have to implement. Got to keep focused on one piece at a time, good advice.

Yes! This is exactly what I'm dealing with. Thanks for the advice.

Well previous devs failed to deliver 3 years after first estimating 1 year, so hope I'm not here that long :~. Thing that irks me is that manager is on my case about running about 2 months behind when the previous guys never delivered anything of real value after 3 years. Good advice though I probably need to communicate this better.

Would love to do that right now, but I'm broke, need to tough it out and see if things improve.

I'm working as a solo developer for a small/medium business and I need to have a rant. I've been at the company for 5 months or so. A little background first, the company's original in-house application was built using MS Access and it was decided to replace it a number of years ago. Attempt 1: Someone was contracted to rewrite the application and to my knowledge it wasn't going well and the company decided to end or not extend the contract and the application was left unfinished with no source code available. Attempt 2: Another developer was contracted later and had previously developed similar software that was to be leveraged and customised for the company. 3 years later (after 1 year estimation) a buggy, horribly unperformant, partially complete application was delivered. Company decides to not continue any longer with contractors. Attempt 3: I come in and inherit buggy mess from Attempt 2. Originally on the assumption I was to complete Attempt 2 and add some features but I find out that a lot of the source code has not been provided because it was previous contractors IP and that the source code I have is a mess. I ask company do they want to continue with the application as is or rip out what I can and repackage it into the long awaited application. We decide to rip it apart to remove the dependency on a closed source poorly supported code base. So I have been contracted for a year to do this and have to deal with: 1. Maintaining compatible UI "feel" and data from original Access legacy application which has poor data integrity and in need of normalisation. 2. Trying to pull code from Attempt #2. 3. A huge feature list and constant feedback like from users like "we really need this" or "it would be great if we could do that", blah, blah, blah. 4. A manager with no understanding of software development or even computers breathing down my neck. 5. Complex requirements and convoluted business logic that are difficult to provide a nice solution for. 6. No other developer to bounce ideas off or cry on their shoulder. :(( I'm losing motivation fast. It is becoming such a huge task and it has been very difficult for me to provide delivery estimates given the legacy system and data, failed attempts, tight time frame and requirements communication. At the start I was too optimistic and was dealing with too many unknowns and now I'm behind on where I want to be, I know that, they know that and I get the feeling they are getting ready to cut me off as well. When I started I could see the w