Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
Slashdot Deals: Deal of the Day - Pay What You Want for the Learn to Code Bundle, includes AngularJS, Python, HTML5, Ruby, and more. ×

Comment Use popular mature open source (Score 1) 257

I have maintained various legacy systems dating as far back as the late 1970s some have faired better than others. By far the biggest difference between those that faired well and those that didn't was continuous supoort. A system from 1990 that wasn't maintained for only a few years due to the false assumption it was being phased was much harder to maintain and than older system which never went out of maintainance.
The popular technilogies faired better than the trendy ones. PL1 Cobol and later C all faired well. Ada not so much. IBM mainframe faired very well. Nonstop servers (HP) not so much. Binary only libraries prevented hardware upgrades even when almost everything compiled properly. If you stick to the popular now yet mature technologies you won't be alone with your troubles down the road.

Comment Swap days with future employer (Score 1) 203

I have arranged this with a few employees from both directions when a replacement was not found in time.
Start doing a few days at your new job early (before the agreed upon date) they don't have to be in a row.
And return these days after a replacement has been found (but no more then two months after you start the new job or such like).
The new employer is likely to agree, it allows you to get into things sooner, and can prevent first week stagnation since you will be on boarding gradually.
It is common after the first day on the job the new boss realizes he isn't quite ready(accounts, training materials, computer, first assignment, ...) on-boarding gradually is easier. You probably can't do more then a handful of days this way but but a few days is much better than none.

Comment Why is Israel not part of the NNPT? (Score 1) 52

6 countries are believed to have held nuclear weapons as of the treay's creation.
Only 5 are recognized as "legitimate" nuclear powers.
Saying if you have them you may keep them but no one else can makes a minimal about of sense. Saying: "everyone who has them except Israel is allowed to keep them" is just plain wrong.

Comment It will be trivial to overcome (Score 1) 150

These glasses may foil current face detection techniques (I'm not even sure about that),
but based on the pictures provided they do not actually conceal from the camera a significant part of your face,
and do not introduce significant variable noise. It should be trivial to adjust face detection and recognition to overcome this
should these ever become popular enough.

Comment lifesize video conference (Score 3, Interesting) 164

I have used pretty much every tool out there skype, goto meeting hangouts to name the more popular ones. But when I did some work with E-bay a while back I got a chance to work with their lifesize system. The camera the screen the high definition and the lack of lag come together to make something far better then anything else I used. I suspect they charge an arm and a leg for such a setup but it works. (I have no financial intrest in lifesize )

Comment Bad science strikes again (Score 4, Insightful) 60

The first hint you get is when you notice this paper was published in a physics journal, not a great sign. Then you actually start reading, and you see they declare LDA as "state of the art". And when you actually read what they propose it is a bunch of standard text techniques which actually work quite well with LDA.
So what they actually showed is that taking vanilla algorithms out of the box without even the most basic data processing under-performs compared to superior data processing attached to a simpler algorithm. Which anyone which did any sort of text processing or any other kind of data managling already new.

Comment It's all about balance (Score 1) 214

Software development like almost everything else is about balance.
Do I refactor/rewrite or not? Add the extra layer of abstraction? write defensively?
Do I commit a partial solution to keep integrated with mainline?
Should I deploy a partial solution to get real feedback?
Do I make it more complicated to handle some future requirement?

The best software developers have a good sense of balance. You can always learn a new language/technology
you can also learn to do things by-the-book learning balance is tricky.

Joel Spolsky says a developer needs two attributes: "Smart" and "Gets things done"
I am beginning to believe the latter is the more important part.

I always recommend new graduates to take their first position in a big corporate environment and their second (and all future) in fast moving start-ups.
After you have learned the "anal" way of doing things you make much better decisions when cutting corners.

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