Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
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 Re:No keyboard? That's nothing! (Score 1) 22

Try migrating from CC to Perforce...
Several hundred engineers have their workflow completely broken (yes P4 is *better* but the devil you know and all that). Productivity tanks for the first month as accidental overwrites of commits and reversions from merges and other wonderful shit hits all the fans...

Comment This method never fails (Score 1) 193

Here's how to calculate a 100% accurate estimate 100% of the time, when your manager asks you to predict how long it will take to implement feature X:

1. Tell your manager you'll get the estimate for them as soon as you've done the necessary research
2. Go back to your desk
3. Write down the current time
4. Implement the feature
5. Subtract the time you wrote down in step (3) from the current time. This is your 100% accurate estimate of how long it took you to implement the feature
6. Email your manager, and let them know the estimate value. If you're feeling like it, you can also let them know that the feature is now implemented (although this may make them feel like the estimate you gave them is no longer particularly useful, so treat cautiously there)

Comment Re:Not just software. (Score 1) 193

For example, if the last time you did it, it took 3 weeks, a good prediction is that this time it's going to take 3 weeks.

Hopefully it will take less, because this time I will be able to take the code I wrote last time and just re-use it, possible with some minor modifications, rather than designing and implementing it all from scratch.

(Or if I can't do that, then either it's a new task and there wasn't actually any "last time I did it", or I did a lousy job last time of designing my code to be re-usable. Software development is mainly about automating previously manual processes so they can be repeated more quickly/easily in the future; that applies to the process of writing the software itself also)

Comment Re:Yes, inherently unpredictable, needs percentage (Score 4, Interesting) 193

I always provide my managers with confidence interval estimated times
50% 10 days (assumes *nothing* goes wrong, no interruptions, and high code reuse)
90% 15 days (assumes no catastrophic issues, no interruptions > 2 hours and only 5 of them, moderate code reuse)
100% 55 days (the wheels fell off, severe schedule impacts of interruptions non stop, no code reuse)

My boss laughed at my 100% estimate until it actually happened.
A lead dev (who could be counted on for sound advice delivered in a belittling way) was struck down by lung cancer and ceased to exist. Another lead dev who was even brighter, and much nicer to work with was poached by a competitor, both within days of each other. The code was cutting all new territory in the system, so maybe 15% reuse? *and* some panicky manager started having $deity damned _daily_ meetings about it.

We almost missed my 100% date, made it by about 16 hours.

Comment Re:That's the big problem... (Score 1) 80

Hell I use it.
Google drive.
I am in a violently bitter divorce and all the docs are on a google drive so I can pull them up on my phone at a moment's notice, while also being able to actually work on them on my PC.

Risk? yes.
Worth it when I can pull up the latest custody order on a moment's notice to demonstrate I do, in fact, have custody of my kids right now? Priceless (and the cops like it too).

Still keep the oblig hardcopy binder like any court system docs, and an offline copy made weekly or when there are big changes.

Comment Re:Finally a good use for fitness trackers. (Score 1) 130

Well yes...
And actually I already have a system I use.
Like you I have a friend(relative) who is responsible for my primary computer stuff, but there is one machine that requires a ping at least once a week or it goes dark, after a month it wipes its keys and my CA signed private key as well.
I'll notice when it goes dark... and if I don't I have *way* bigger problems.

Comment Re:Retard (Score 1) 102

If the switch happened *after* the ASIC was created then yes.
If the algos are all defined then I just build an asic that does the following:

get input
switch (input.algo){
case Algo1: { foo();break;}
case Algo2: { bar();break;}
case AlgoN: { doN();break;}
default: {awNuts();}
put output

Sure the ASIC is bigger (and costlier), but each of those algos is a hardware implementation optimised for nothing else.
An ASIC is (basically) a slice of a RISC that does what you want with nothing else.

In fact you can think of a RISC as an ASIC implementation of CISC.

Comment Re:Choice (Score 1) 259

If I hadn't commented already I'd mod you up. I think those dismissing this out of hand have never experienced it. Extreme stress and a loss of self esteem can make things seem much darker and choices much more limited. I imagine that suffering that when you think you've just reached the pinnacle of your career would only make it seem worse.

Slashdot Top Deals

Asynchronous inputs are at the root of our race problems. -- D. Winker and F. Prosser