Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 internet speed test! ×

Comment Old old OLD news (Score 1) 268

Since the 1800s, robots started taking over human craftsmanship jobs:
- making cloth
- making glass bottles
- making paper
- farming
- making nails and horse shoes
- making cars
- making (just about anything)
Since the 1900s, robots started taking over human service jobs:
- typing documents
- filing documents
- sending messages (postal service)
- handling financial transactions
- store clerks (e-commerce web sites)
- marketing
- distributing news

I'm sure there are many more jobs that have been automated, that I've missed. Yet somehow we have very close to "full" employment. Our collective standard of living is higher today than ever, even for the poorest among us.

The robots are coming, this is true. I say this is a good thing! We humans have brains, we will find something better to do than the drudgery that the robots are taking over for us.

Comment Not bugs until they cause problems (Score 1) 266

The rule of thumb for programming anything is, first make it work, then make it work better / faster.

If the first pass works well enough and fast enough, it doesn't matter if the code was written an efficient manner. If somebody used bubble sort for an array of 5 items, who cares? If the array becomes larger, now you have a performance bug.

It's literally wasteful to spend time on performance enhancement before you know which performance problems actually occur in real life. Another name for premature performance enhancement is "gold plating."

Comment Honey pot (Score 1) 415

Password managers, especially cloud-based, provide a huge honey pot for hackers. Regardless of the encryption algorithm used, there is ALWAYS a weak link in the chain somewhere. Remember Heartbleed, or the LastPass hack of 2016?

If you must use a password manager, use a lesser-known one, because these will be a less-attractive target for hackers. Or try storing password hints, so the actual password isn't stored anywhere.

Comment Ideas are a dime a dozen (Score 4, Informative) 154

It's execution that's hard. Sure, the person on the shop floor or in the cube farm might have an idea that seems great, but making that idea happen politically within the organization is very, very hard. People don't like change. That "good" idea might be somebody else's worst nightmare, and they're going to fight tooth and nail to keep it from happening. This isn't necessarily a bad thing, it's just reality. That's why people who CAN change things become the leaders.

Comment The easy part (Score 1) 132

While what this kid did is impressive, he's only done the easy part: getting a car to drive itself under a limited set of circumstances that he knows about.

The hard part is to get a car to drive itself under all sorts of weather and road conditions, and safely handle all kinds of expected and unexpected road hazards, such as potholes, people, bicycles, and crazy drivers.

Comment Population of Github users (Score 3, Insightful) 149

Github is especially popular with the Linux crowd. It was, after all, invented to improve development coordination of Linux.

This population skews the results in three significant ways:
1. Towards obscure and fad languages. This is linked to the extreme fracturing of Linux programmers, each group of which fiercely promotes its own favorite language and tools.
2. Away from Windows. GitHub is especially popular with the open source crowd. This means that C# and .NET languages (favored by programmers who want to make money with their code) will be underrepresented in the statistics.
3. Away from projects developed by less-than-genius developers. GitHub still has a steep learning curve for a lot of developers to master, especially those who have been raised on TFS and SubVersion. The obsession with cloning and branching is foreign to these programmers, and they often don't see the point. These types of programmers are typically creating relatively straightforward Web applications, and tend to write their code in C#.

I suspect that the real numbers for weekend coding would feature Microsoft .NET languages much more prominently, if all types of repositories could be counted.

Comment Re:No if so add 20-45k (Score 1) 435

That doesn't make it honest. Honesty is still important to some Americans. Sure, the company may be out of bounds when they ask, but at least they aren't being dishonest! If you lie on your resume, but you expect the company to be honest and up-front with you, you're being a hypocrite. If you're willing to lie on your resume, you're probably willing to lie about other things. You'll get away with it sometimes, but eventually it does come back to bite you.

Why say anything at all? Leaving the fields blank is just as effective, as a negotiating tactic. Those "extra" fields are usually stupid anyway, nobody actually cares whether you put a number in the box or not.

Comment Why ask why? (Score 1) 435

Your salary history (with the possible exception of your current salary) is none of the employer's business. Don't ask about it, just leave the fields blank, make them come back to you and ask for it if they really want it. This puts YOU in the driver's seat.

In school, there was always that student that would ask the teacher if there was any homework, as the class was ending. Don't be that guy!

If you don't want to talk about your salary, just tell them what you're looking for. Make sure that amount is in keeping with the normal ranges for your years of experience, and the area where you live. The business is doing their homework, they know what you SHOULD be making.

Slashdot Top Deals

"The value of marriage is not that adults produce children, but that children produce adults." -- Peter De Vries

Working...