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

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: The danger of ngXYZ (Score 2) 232

by mtippett (#49377115) Attached to: Why You Should Choose Boring Technology

The same thing happens with the hope for the "next generation" product solving all the ills of the current generation. Or the assumption that the code you have inherited was created by fools a number of years back.

The reality is that software has a set of maturity related bugs and a set of structural, intractable issues that are related to the design and architecture of the system. Each piece of software has it's unique set of intractable issues.

Software that has been in production has typically reduced it's maturity related bugs. The software built on top or that integrates with it is built around those intractable issues. When you move to a new piece of software - either a new architecture or the "groundbreaking ng version of XYZ", you end up with swapping a set of *known* intractable issues, for a set of *unknown* intractable issues plus a set of maturity related bugs.

Similar to TFA, the risks of old+known vs new+immaturity+unknown needs to have another factor similar to "value-add". If the value-add *really* adds a lot of stare the risks in the eye and march forward. If the value add is marginal, make sure the meta-benefits (performance, maintainability, etc) are clear and understood, otherwise you may be facing a train wreck of an upgrade.

Seen it many times, always wary of the ngXYZ project...

Comment: Purple Unicorns and the Meat Grinder (Score 3, Interesting) 292

by mtippett (#49217393) Attached to: Do Tech Companies Ask For Way Too Much From Job Candidates?

Reposting as a non AC.

There are some reasons for the unrealistic job descriptions, they are a lure, and are generally loosely associated with the role (ie: 80%). We're hoping for a purple unicorn, but know that they don't exist. But would settle for a winged horse, a unicorn, a purple horse or more realistically a good horse. But occasionally one of the unrealistic mix of experience does come through.

It has been almost a decade since I last went through an applicant list for a particular role.

What happens most times now is an application is added to an applicant tracking system. This parses the resume (from word, pdf or text) and creates a database of candidates matching keywords. This meatgrinder approach means that when I am looking to fill a position, I don't actually look for applications - I might - or the HR might quickly review the actual applications. What I do is search and screen. Search for a set of keywords, and from that list look for obvious issues (applicants to every job, rejected candidates, age of resume, etc). And then the HR recruiter will screen down from there.

I'll typically get 20 or so resumes to review. The recruiter may review 100 to 200 resumes. There pool of candidates may be 2000 to 3000 of which only a small portion are for my position.

This is part of the reason that resumes have gone from minimalistic to more fully descriptive with keywords sprinkled throughout them.

Comment: Automation is Dependent on Design for Manufacture (Score 3, Informative) 187

by mtippett (#49157459) Attached to: Foxconn Factories' Future: Fewer Humans, More Robots

I've been to Foxconn factories in Shenzen, and there are clearly opportunities for deeper automation. However, this will only be possible when the underlying hardware design has been designed for automation.

At the PCB level, pick and place achieves amazing automation and performance with smaller than rice-grain size components used in modern electronics. That is a given.

At the assembly level it isn't so easy to automate with a lot of the designs. There are flex cables, adhesive, torque sensitive screws that all rely on a human to be able to manipulate and then quickly respond to misalignment. To automate this, the design constraints placed on the Industrial Designs need to change. For low and mid-range products where form is not at the level of Apple integration, this will probably increase the automation. For the high end where every mm counts it's unlikely that there will be a high level of assembly automation.

Comment: Round Hole, Square Peg.. (Score 1) 193

by mtippett (#49089573) Attached to: Human DNA Enlarges Mouse Brains

I'm not anywhere near knowledgable about medicine, but if the brain is larger, does the cranial cavity grow increase to the same level?

I wonder if there a round hole, square peg kind (big brain, small cranial cavity) of issue coming. The brains might be smarter, but they may suffer from decreased mental abilities from intracranial pressure.

Comment: Able to Code != Professional (Score 1) 546

by mtippett (#47819477) Attached to: Does Learning To Code Outweigh a Degree In Computer Science?

Title aside, the ability to code is a workplace requirement, and if you are not looking at traveling/work internationally, you aren't going to get very far without a degree.

Some of the "college drop out" success stories are no longer just coders. They are now C-Level executives, different rules apply. If you don't have a degree then in general you won't be eligible to get Visas to work in other countries.

Independent about how good you are, without a degree you are restricted to your local geography (country, etc).

Comment: CVSS, CVE, CPEs and Policy (Score 1) 84

by mtippett (#46901707) Attached to: Ask Slashdot: How To Communicate Security Alerts?

Define actions (instant, daily, weekly alerts) for ranges of CVSS scores http://nvd.nist.gov/cvss.cfm?c...

Track incoming CVEs (http://nvd.nist.gov/download.cfm) , assign CVSS scores specific to your organization. Also have a organization specific remediation approach.

As you find out who is using what software, and use the CVE CPE (http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-2168) information to target more specific users.

In the blast emails, you could potentially harvest who thinks they may be affected to gather CPE information.

It's going to be a thankless, painful job, so you may as well automate as much as possible.

+ - Gamifying the Workplace: Badges IRL with 3D Printing->

Submitted by mtippett
mtippett (110279) writes "The problem with the virtual badges is that they are too cheap to make (effectively free to create a new one) and only appear when you go to a users' homepage. Having played with 3d printing, I realized that you could make these badges in real life and bring a bit of physical interest to the work place, applying the same rules. With a few minutes on an online 3d modeling tool, online 3d printing services, and finally a magnet and some super glue, you can easily end up with full color sandstone badge."
Link to Original Source

Comment: Not going to be mainstream. (Score 1) 139

by mtippett (#46820431) Attached to: Google's Project Ara Could Bring PC-Like Hardware Ecosystem To Phones

There will probably be a market for this in the tech enthusiast. But it will be highly unlikely to go mainstream. Mainstream (iphone 5s) is 7.6mm thick and weighs. According to http://motorolaara.com/2013/10... it is probably about 9.3mm - effectively as chunky as a 2 year old device.

What may evolve from this is specialist hardware and specialist configurations.

Some interesting spin-off technologies might be high speed bus interconnects (thunderbolt 2), modular and novel hardware configs (3d scanning - project tango, yotaphone - e-ink backside). Ultimately, enabling technology advances is what google spends it money on these days...

Comment: Polishing old code or writing good code (Score 4, Interesting) 139

by mtippett (#46774589) Attached to: Code Quality: Open Source vs. Proprietary

The report doesn't really go into an important measure.

What is the defect density of the new code that is being added to these projects?

Large projects and old projects in particular will demonstrate good scores in polishing - cleaning out old defects that are present. The new code that is being injected into the project is really where we should be looking... Coverity has the capability to do this, but it doesn't seem to be reported.

Next year it would be very interesting to see the "New code defect density" as a separate metric - currently it is "all code defect density" which may not reflect if Open Source is *producing* better code. The report shows that the collection of *existing* code is getting better each year.

Comment: Re:Genomic Medicine will probably be required (Score 1) 157

by mtippett (#46639189) Attached to: Should Patients Have the Option To Not Know Their DNA?

That is different. My read of the GINA is that your health insurance provider is not allowed to use genetic screening to make coverage RISK decisions. As in, they can't force or require you to screen for cancer and then decide that you aren't coverable because of BRCA. Apparently life insurance is not covered by GINA, so that is another issue.

Also note that GINA is an American law. Not global.

The comment I made was about tuning treatment based on genetic information - which is very different. Rather than a cocktail of drugs to suppress and support different side effects and responses - you can more targeted doses to resolve your direct issue. Warfarin is a good example, too much doesn't help, too little doesn't help. Your genes help identify what your correct dose is.

Comment: Genomic Medicine will probably be required (Score 3, Insightful) 157

by mtippett (#46636569) Attached to: Should Patients Have the Option To Not Know Their DNA?

As Genome Wide Association Studies begin to crack more of the genomic puzzle, there will be tighter and tighter direct correlation between medicine types & doses and the effectiveness of those drugs. As this efficacy increases, it is highly likely that the best insurance coverage will be based on genomic information.

Determining precise doses of a drug and which drug should be used is going to make for much better quality of medicine. I would expect that in a couple of decades people are going to look at the drug practices of today and laugh that we are pretty much throwing darts at the drug dartboard and choosing whatever it lands on.

Opting out of specific tests will be like not wanting X-Rays to see if a bone is broken.

Comment: Re:Amazing (Score 4, Interesting) 400

Well for commodity items - I get your point. However, my personal experience is owning a house that has a really unusual shelf pegs. Unusual in that they are simply not available. I ended up modelling them and using shapeways to print them. What I made is up at https://www.shapeways.com/shop....

The cost, was about $2 per peg - which is about the same cost as low run retail products at home depot.

3D printers will make it affordable for extremely low run prints. For spare parts and out-of-production items it removes a lot of obsolescence.

Theory is gray, but the golden tree of life is green. -- Goethe

Working...