C is fine ... I use it and will probably keep using it for a few years more. But usually printf in my system ends up in stack overflow, on 8 core 1GHz 2/4/8GB memory.

I was always amazed how at this job I'm still around a few hundred euros per line of code after 3 years; I'm pretty sure I've written more lines in Word and Excel. I miss writing code, somewhat, but I've learned so much more by debugging. The most important is that I really miss debugging in Visual Studio :laugh: ; loading 20 meg binaries over JTAG and sometimes not having a working debugger is a pain, a fun pain. Not my fault they use me to put out fires.

The anti-Kiev fighters had just bragged about capturing some Buk systems. And as far as I know they have no airforce so the govt forces don't need to use SAMs. They also bragged about downing a plane other than the Su-25 and hastily deleted the brag once news of civilian aircraft vanishing appeared :D

Nooo, recovering from a cold and you just reminded me of another good reason to be at home. Very nice for cold times. Have pitty on the poor folk at workplaces that don't allow alcohol as a refreshing beverage during work hours.

One so far. Solved it by sweeping it under the rug (customer request). 5 months of work. 2 people tried their hand at it. Still as much of a mystery. I would have still wanted to figure it out but lack of source code for the entire app (only ran at somebody else site) and the fact that it was tested on weekends only and it didn't show up every weekend of tests made it pretty rough. Worst that I've solved was about 2-3 months of work, and it was a stupidly simple root cause from the customer's side.

Vunic wrote:

* He leaves home early when his peers work days and nights to complete their tasks to meet their daily schedules. (just like how Bruce lee stays unmoved seeing a silly street fights.)

I would do the same to be honest. I do not care much for projects I'm (or good senior devs/architects) not involved in estimating the duration of or that seem terribly out of sync with reality. That just shows complete failure from management. Managers like that do not deserve respect or overtime, it's on their heads. I would on the other hand work overtime without pay if shit hit the fan with something unexpected which goes above the 25-50% risk already included in the estimations (even if those can sometime be traced to poor understanding from the team that estimated the project). Maybe I'm just too spoiled with good managers that prefer projects on budget and on time rather than on time and screw the budget (overtime work is quite expensive).

I have been programming for 20 of my 30 years (hobby, academic competitions, some random apps for acquaintances). I have crawled my way through University. But, I have learned work ethics while working, mostly without hindering product timelines (I hate not finishing something I already said I will finish at a specified date, plus close deadline -> best focus). I know very few good programmers that did well in Uni. I also know very few good programmers that did badly in Uni.

Why does your boss tell you how long a project should take? He can tell you how long he'd like it to take but I see it as: 1. Customer asks Sales 2. Sales asks PM 3. PM asks senior devs/architect - initial estimates with included risk from the devs' experience. 4. PM answers Sales with %-age risk included, based on how scared the devs looked. Decision on initial team size maybe (how many available, how much can be done in parallel, available sprints). 5. Sales answers customer then bills if customer agrees. You skip devs' estimate or skip PM adding in risk, you're screwed, been there, done that. Project was on time but 30%+ over budget. Would have been more if the devs on it would have actually told the truth about the extent of their overtime.

He had 7 years to learn. Why assume he's the same person he was then? Plus why care who gives advice as long as it's good? You can think for this very reason, to pick up knowledge and filter on usefulness.

Of course you can. They're pretty much identical. The only thing different is who preaches and what they want to preach. I think Christianity 1k years ago was pretty much what Islam is now in some countries, immoral, self righteous, bent on enslaving people by denying education. Noticing this paints a clear picture on how much humans can corrupt such a simple and peaceful message presented by some religions. The created the holy books, they distort the holy books because they can't admit the message itself is distorted by the writers human nature/culture/experiences, they change everything to just fit how they BELIEVE their thing should be.

1. Ask if the issue/feature has appeared before and therefore might not need new code/much work. 2. Work on it assuming 1 is bad. 3. Ask once you've tried some stuff. Not without trying though. It's quite annoying to ask for help when you've tried nothing and expect everything to be served.

Maybe once I'm a grumpy old man with no desire to learn anything new I will let them quiz me but until then my memory is no measure of what I can do. But I guess at that point I will have given in and accepted a managerial position. Right now I am happy I have a manager that takes all the crap for us.

I have never had a "proper" interview. No tests, no whiteboard code, no brain teasers. Well, I'm lying, there was this one place but I ended up refusing them. I didn't do that well with the code I had to write on paper. And I could see they weren't happy with my weird answers, or my 0 knowledge in a field I'd been working for 3 years at that point. When asked what does function "x" do, I said I don't know, I never bother remembering, I just check the API when I need to use it. When asked what API function I'd use for something I said "I don't know, I search API, I google and I select the best option in my opinion". They really weren't happy. They did offer me a job, not that well paid. I called them on the signing day and told them I don't want the job. Real reason was I'd found another job where I went in with 0 experience (web dev previously to mfc c++). That other job the interviewer (my future boss) asked me a couple of tech questions which I barely answered (what is malloc, new etc), I mostly guessed what they should do. I never saw that condescending look on his face. Then it was "What do you want in this job?". And I answered "To learn as much as I can". Hired. 2 weeks later I was working on real projects. First job was on a file sharing site and the interview scheduling happened at 3 AM. The boss saw some of my PHP learning code and told me he was impressed that I was actually organized in a learning project (separate files by functionality, display functions separate from logic - I still have no idea what MVC MVVC and that other crap means). That learning project was a discussion forum written from scratch. Current job I was recommended and the interview was a discussion on what I like and how I'd do certain things and arguments in why one way may be better than another for a certain given design and requirements. For some reason I was hired as a senior, with close to 0 C experience even though all I do is C and various flavours of ASM. I also pretty much never had issues with people in the teams I worked in. There's just nobody I actually dislike. As for the ones that are slightly slower, or know less, you help them even if that means a couple hours unpaid overtime to finish your work. In the end the team benefits, the project(s) benefits. As for when I'm slow or know less, I ask my team and if they can they help. In the end I'm pretty sure I would fail most "proper" interviews. I just can't get myself to care about preparing for an interview, it's such a complete waste of time to le

Array indexing is completely irrelevant to understanding why and how the little monsters on that printed page to what they say they do when ran by a computer. A very clear/clean language and good writing skills are the best tools. There should be no malloc/objects/elevated language paradigms in learning programming from 0. The hardest thing ever is figuring out why i = i + 1 is allowed.

Question: Since when does the manager estimate time remaining on work. Other than the deadline if it can't be helped. But I've never ever heard of a manager telling a dev how long the work would take. At most there's a negotiation if the manager feels it might be too much on the estimation. Or if the dev feels the previous estimate was wrong. I would instantly resign if anyone did that to me. Any barely decent manager should know they have no idea how long implementation takes and to listen to the devs.

I would have asked for a 20% raise and to do whatever I please with my desk, to stay.

Hmm, best way to redirect that I found so far was injection into IP stack. Not sure it still works on Win7 but damn that was hard to track down when I got it like 6-7 years ago. Fun though, tinkering is always fun.

Hahaha, so familiar. When you need proper hardware support while writing software for a client on hardware someone else makes you CC your client's engineers. The wheels will spin faster than you ever saw them spinning before. Few million worth of client seems to do that (even though there isn't a chance of cancellation, the relationship is too old, too big and there are very few that can do hardware even remotely similar). On the other hand we've found 1 hardware bug for them and a few missing items in documentation so it's not like they didn't gain anything.

There's a couple of ways US ambassadors call lobbying when in Romania (when talking about Romanian politicians): corruption, influence trafficking. We do not have a lobbying industry but everyone has friends who have friends who ...

Please tell me that's not over wireless (even if the speed is surprisingly familiar for wireless copying).