. said:

You are so naive. You know how long it takes to publish a book? Up to a year. You might as well go study cobol or something, any book you read will be just as obsolete.

. said:

You guys need to start working with the cloud. Everything will be the cloud. Apps will be seamless because of always on Internet access with no lags or downtime higher throughput and enhanced operating synergies.

. said:

you're trying to be funny but people who want to keep their skills going in the right direction need to spend some time on the major cloud platforms.

Finally, some practical advice. I don't know how valuable it is, but at least it's something. Thanks.

. said:

. said:

You are so naive. You know how long it takes to publish a book? Up to a year. You might as well go study cobol or something, any book you read will be just as obsolete.

stop being a jackass.

. said:

you're trying to be funny but people who want to keep their skills going in the right direction need to spend some time on the major cloud platforms.

. said:

Not being a jackass, dude. I couldn't even keep up with my legacy software by studying books. A goddamn cobol programmer would get fired for not keeping up to date if he relied on reading the latest cobol books.

. said:

simply wrong. there is a sure fire way to skilling up.

1st, you find *the* book for the language. There is always one. It does not change except for edition. read that book and learn it well.

2nd, you hit the web and work tutorials and pick up jargon and trends.

3rd, you write 3 or 4 things you already know how to write in the languages you've been using.

assuming you are not completely socially inept using this methodology will let you walk into 99% of the jobs out there.

. said:

I can vouch for this. I learned to program by reading free online tutorials. I only buy books that are universally considered to be the definitive text on a subject.

People ask me why I'm "reinventing the wheel" when I write something for which several solutions already exist. I tell them it's because I want to learn how they did it.

The code I was working on when I was unemployed helped me get my current job.

. said:

simply wrong. there is a sure fire way to skilling up.

1st, you find *the* book for the language. There is always one. It does not change except for edition. read that book and learn it well.

2nd, you hit the web and work tutorials and pick up jargon and trends.

3rd, you write 3 or 4 things you already know how to write in the languages you've been using.

assuming you are not completely socially inept using this methodology will let you walk into 99% of the jobs out there.

. said:

I can vouch for this. I learned to program by reading free online tutorials. I only buy books that are universally considered to be the definitive text on a subject.

People ask me why I'm "reinventing the wheel" when I write something for which several solutions already exist. I tell them it's because I want to learn how they did it.

The code I was working on when I was unemployed helped me get my current job.

. said:

wait, so, working at a large company fucks you?

Try working for government or the military. You get amazingly proficient at things NOBODY else uses.

. said:

wait, so, working at a large company fucks you?

. said:

. said:

I can vouch for this. I learned to program by reading free online tutorials. I only buy books that are universally considered to be the definitive text on a subject.

People ask me why I'm "reinventing the wheel" when I write something for which several solutions already exist. I tell them it's because I want to learn how they did it.

The code I was working on when I was unemployed helped me get my current job.

Well, ok. I'm sure that could get you a beginning programming job. I guess it's been too long since I was starting out.

. said:

They don't stay trevs long. They realize what bullshit it is and move into management.

All the scared pussies stay at their same menial jobs until they get shitcanned at 40. Then you see Manpower pimping them out at $10/hour.

. said:

Try working for government or the military. You get amazingly proficient at things NOBODY else uses.

. said:

. said:

They don't stay trevs long. They realize what bullshit it is and move into management.

All the scared pussies stay at their same menial jobs until they get shitcanned at 40. Then you see Manpower pimping them out at $10/hour.

I'm sick of this shitty troll. Trevs are far more useful than management. Low level Managers are always the first to get shitcanned unless they suck a mean dick and swallow.

. said:

They don't just dismiss it. They yell and scream about it. They literally don't have a clue about what you do, but if you say anything they treat it as insubordination.

Once, for an hour, a boss kept demanding of me why he should upgrade 10 year old software.

. said:

I'm sick of this shitty troll. Trevs are far more useful than management. Low level Managers are always the first to get shitcanned unless they suck a mean dick and swallow.

If you're a rock star in big tech you move up the old fashioned way. If you're just a guy who's not going to make it into the executive ranks then keeping your technical skills sharp will make you far more employable than people who've gone the mgmt. route.

. said:

Yes. You have to stay hungry. There's no resting on your laurels in this racket.

Tell me about it. I have 4 fucking servers at home. I worked hard keeping up with that shit.

Oh, wait, it's all obsolete. Software development in my industry is done on virtual servers.

. said:

Funny that mastering a ubiquitous yet simple CMS like wordpress or drupal can net you unlimited work opportunities,..yet working in some super advanced, convoluted, proprietary environment for years you can wind up in a dead end.

I made sure to know every web CMS out there, means you can basically write your ticket on all the work out there.

. said:

. said:

They don't just dismiss it. They yell and scream about it. They literally don't have a clue about what you do, but if you say anything they treat it as insubordination.

Once, for an hour, a boss kept demanding of me why he should upgrade 10 year old software.

Evidently your communication skills suck ass. You should have been able to explain it in under 50 words.