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 799.9 of them were going to fail anyway (Score 1) 177

I kid, I kid. 760 would fail anyway.

But really "startups" in the technology sector are supposed to be "disruptors" so wouldn't it be the job of a startup to take the current situation (be it net neutrality or Cable-Company controlled blood-letting) and turn that into a surprising profit model that exploits some weakness or failing of the status quo?

The tighter Comcast squeezes the rock, the easier it should be to wriggle through the cracks in their failing business model.

Comment Dagny Taggart did it (Score 1) 81

The second most ridiculous thing in "Atlas Shrugged" was that Dagny Taggart invented a perpetual motion train "powered by ambient electricity in the air."

Of course the most ridiculous part was the part where CEOs joined together to create a utopia in Colorado with no poor or working people, just their own bootstraps, where they presumably ate nothing, repaired their own lavish houses, and needed no help from tradespeople, doctors or other "takers" who were not rich CEOs and obviously just wanted a handout.

Comment 2007: Writer's strike caused the 2016 election. (Score 1) 192

During the last writer's strike, NBC un-cancelled "The Apprentice" (which had low ratings) and aired "Celebrity Apprentice" during "Must see tv" Thursday.

Trump would not be president today if NBC had decided to pay their writers instead of airing cult-of-personality bullshit.

Comment Re:This is horrible (Score 1) 90

In Dallas I live 1/2 a block from the bus stop, and worked in a building off the same bus line. This is the best possible scenario for public transit in Dallas, and it took 1 hour and 15 minutes to get to my work, at a cost of 80 dollars per month when prepaid (or 5 dollars per day). Conversely taking my car it is a 10-15 minute drive to work and about 30 minutes home (worse traffic).

That is before I changed office buildings. At the new building, my car commute is the same. On a bus? Almost 2 hours, including 2 bus changes, and 1 mile walking.

My commute at both offices was one of the best of any of my coworkers.

Dallas is big. the Dallas Fort worth area s gigantic. It is 1500 square miles of solid suburb with the occasional high-rise. and it is almost impossible to survive without a car. Uber helicopters will not change that.

Comment Re:I wonder... (Score 1) 450

In my experience as a team lead/hiring manager:

* We had a simple test that any developer should expect to pass.
* Hiring with highly competitive wages and benefits in one of the top tech markets in the US
* We only interviewed people with a degree in computer science
* We had a lower than 20% success rate at candidates writing working code (even ignoring syntax problems and semicolons, and just looking at logic flow)


What was this massively hard test?
1) Write a function that uses recursion to output the Nth iteration of Fibonacci (test includes full explanation of what fibonacci is)

2) Write a function that determines if a given year is a leap year (test includes full explanation of how to evaluate if a year is a leap year)


Nothing tricky at all, a simple "have you ever written code, and can you follow instructions/requirements?"
My 11 year old can pass this test. Tons of people with "Master's degrees" and "10 years experience" have no idea where to start.

It is not shocking that 95% of developers from *ANY* pool of people are worthless. It is not limited to any nationality or country of origin.

Comment Distraction from:The Promise reviewing poorly. (Score 1) 482

This seems to be an article about brigading; but it is not. This article is an attempt to get ticket-buyers to distrust movie reviewers by inflating the perceived effectiveness of stupid IMDB reviews.

Look, Turkey is fucked up and the Armenian Genocide is a real thing that is important. This movie is mediocre at best, according to a bunch of movie reviewers who are probably (almost certainly) not on the Turkish government's side.

It can be both: Botters could have deflated the IMDB rating and the movie could still be bad.

IMDB ratings are garbage, professional movie critics aren't that great either, but they are also not under the sway of the Turkish Propaganda machine, and they think it is a boring cookie-cutter movie.

So I would say it seems more likely Hollywood is gaming the battle against critics, by exposing online trolls, and using the narrative in its own favor.

Comment Well-defined Devops. (Score 1) 313

Developers code. Developers review code. Developers write code to test code.

Developers can't touch production.
Automated checks of ANYTHING are golden because you aren't relying on people, and you aren't pitting people vs people.
It is all about consistency when you boil down to the bones of a well-running team.
Start with those rules and actually follow them and you end up with a pretty awesome setup, because Developers will naturally gravitate to defensive, test-driven programming when those are the rules.

1) All code is reviewed before it is merged, this is easily enforcable in bitbucket or github, probably others, but use one of these two anyway. It won't stop all your problems, but it is great triage and it forces lone-wolf mitigation. I don't even care if the reviewer is an expert... this isn't a gate keeper activity as much as it is a sanity check. "hey why did this variable get set, then re-set before you checked it?" or "hey how come you deleted 90 source files?"
2) All your code goes through some kind of code-quality gate like Sonar Qube or some other Linting tool. This can find and highlight common mistakes, and get them fixed before they are even reviewed. Developers hate to modify a pull request, so give them as many free "oh if I fix this nobody will bother me" wins
3) All unit tests must pass before code is merged. This is slightly tricky but you are going to need Jenkins or some other tool that is not as widely used as Jenkins; and integrate it into your bitbucket/github.
4) All deployments are automated. Sure you can have someone push a button, but they shouldn't have to fiddle with anything. And whoever is pushing that button can't be a developer.
5) Since your deployments are automated, your QA system is exactly like your production system (but maybe smaller scale) this way you are actually testing the thing as it will be deployed. "Kinda sorta how it will work in prod" is never a good test. If your QA deployment is automated, and the deploy is broken in QA, then you have to fix it before it goes to prod. Ideally your developers can't touch QA either, but you can work toward that.
6) Since your developers aren't touching production, they will be forced to do things like: write actual helpful log messages, not make code changes that break the deploy, and reproduce production problems in Unit Tests so they stay fixed forever.

Slashdot Top Deals

No amount of genius can overcome a preoccupation with detail.

Working...