Forgot your password?

Comment: Google? (Score 1) 479

by Dishwasha (#47980791) Attached to: Ask Slashdot: Finding a Job After Completing Computer Science Ph.D?

Or any place that writes database software (i.e. Oracle, pick any NoSQL company)?
Or any place that needs people who can do weather modelling?
Or any place that needs people who can do HPC (i.e. computational science; a little redundant from the question above)?
Or any place that needs software "architects", not developers?

With a Phd (not to be confused with Phb as they only get master's degrees) there's no need to slug it out in the trenches with us mere mortals who often find Knuth difficult to follow.

Comment: Re:How much money are we talking about? (Score 1) 387

by Dishwasha (#47868887) Attached to: Unpopular Programming Languages That Are Still Lucrative

Let me put it this way. With such languages you can break in to the 36% Obama 2013 MFJ proposed tax bracket and you don't even have to be living in the greater Seattle, Washington area.

I think once you're at a certain level, you must be multi-disciplinarian in languages, libraries, and frameworks. You're also primarily getting paid well because you're a good software engineer and even better at solving the business's problems elegantly and with the least amount of effort.

Working in a smaller pool can be good because scarcity drives demand. If you're in the larger talent pool you have a lot more competition which actually drives down wages, especially when you're getting edged out by dirt cheap H-1Bs.

Comment: Re:My opinion on the matter. (Score 1) 826

by Dishwasha (#47751357) Attached to: Choose Your Side On the Linux Divide

I could be wrong, but I believe systemd came out of the Redhat camp where they continuously struggled with the inability to query and manage system state for total system automation (i.e. cloud). systemd was the answer for Redhat, yet somehow everyone else starting thinking it was the answer for them too.

Comment: Ask your customers (Score 1) 199

by Dishwasha (#47672305) Attached to: Ask Slashdot: Should You Invest In Documentation, Or UX?

Instrument your documentation pages if they're online. Put high priority focus on the most used pages for your initial roll-out if that makes sense. Have your Product/UX team talk to clients and see if they find the documentation useful and make sure they have a decent quality sample size. Talk to customer support to see if customers are calling in with questions that was available or not available in the documentation. Measure cost to customer benefit and client retention and if you don't know how to constructively do that, don't change how you're doing things until you do.

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (10) Sorry, but that's too useful.