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


Forgot your password?

Comment Re:Here's a thought... (Score 1) 161 161

When you're a kid/teen you don't know what may be an embarrassing photo or video. That's what being a kid/teen is about. The video you put online, discussing international politics with your impeccable 12 year-old wisdom, may have been the proudest day of your life. ... 10 years later and it's a cringe-fest that makes you appear to be an idiot who's a little bit racist.

You get older, you learn something of life, you realise that aged 12 you knew nothing, and you'd rather no-one was watching that video. It does not represent who you are now. What's wrong with wanting it gone?

Comment Not practical (Score 1) 278 278

It's not practical any more than everyone learning to be lawyers or plumbers or electricians. Get experience and master your art rather than try to be a jack of all trades. Newbie programmers usually do poor work for a while (or are slow), just like newbie plumbers.

Comment Re:funny I should see this right now (Score 1) 108 108

mongodb? Use something that's been tried and true for at least 10 years. Go with MySql or PostGresql and screw the noSql toys until they mature and have decent docs.

Let pioneers take the arrows, the rest of us stay in proverbial Boston, which has infrastructure and seasoned specialists, and get shit done. And we have nice lawns to kick fanboys off of.

Comment Re:Here's the list (Score 1) 108 108

The problem with most software isn't that it can't be modelling and rely on basic physical principles, it's that many projects fail to take specs and testing seriously

Most requesters (users) don't really know what they want UNTIL they actually see something concrete, and then realize it didn't fit what they had in mind. We don't need engineering, we need mind-readers. If users had enough time to sit and be thoroughly interviewed about needs and preferences, they wouldn't need automation to begin with.

And further, how to make software maintainable in the longer run is highly disputed largely because it depends on "wetware" and unknowns, such as developer perception of code, and unknowable future domain changes.

It's more akin to writing technical documentation than to building a bridge: how do you write documentation that's clear to the audience, but flexible enough that it doesn't have to be largely reworked for every change.

There is no magic modularity formula: domain issues inherently intertwine (or can intertwine in the future even if not at original launch.) You can't hide intertwining, you have to find a way to manage it well.

Comment Humans (Score 1) 108 108

Software development seems to be riddled with arrogant know nothings who think they can cut corners or reinvent the wheel...

That's a problem with human nature, not just devs. We are not Vulcans. Humans are impatient, egotistical, fixate on the wrong factors, and often just plain random; and most don't know it or care.

I know some well-educated people who are complete idiots outside of their narrow specialty. I'm probably an idiot also in ways I don't even realize (please don't educate me in replies). My head-model of the world is perfectly logical and consistent to me, but it's probably highly lossy against the real world.

Gee, it's almost as if we are merely upright apes who happen to be able to talk and write. (I would have said "hairless", but I'm hairier than the orangutans I see in the zoo.) They fling poo, we fling nukes.

Real programmers don't bring brown-bag lunches. If the vending machine doesn't sell it, they don't eat it. Vending machines don't sell quiche.