Slashdot videos: Now with more Slashdot!
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).
1) Calculating 1MB of data and writing it to disk
2) Calulating 100K of data, writing it to disk, repeat 10 times.
If the time to write to disk is what takes most of the time, then getting the operation started early and writing to disk in parallel to calculating your data will always win. In their case - what they have done is made the in memory operation exceedingly stupid so it takes too much time. I could trivially write C code that blows their operation out of the water, unfortunately - their Java/Python code are hiding a LOT of inefficiencies in the in-memory operation. So compare their disk operation, with a cache line optimized in-memory calculation and a disk cache optimized disk write operation... It won't even be close.
That said - most engineering organizations have documented a process and adapted one of many tools to support this process. Sounds like in this case they don't even know what the process is - heck, everyone probably does their own thing so there is likely to not even be a process.
Step 1: Determine how you want issue tracking to work
Step 2: Get everyone to follow this process without bringing in a tool, your process will change during this step
Step 3: Document the final process from Step 2
Step 4: Bring in any tool that can be lightly customized to support the documented process
Note the hopefully lightly customized part above... Yes there is probably work to do here, regardless of what tool you choose. Most likely you want to pay for the tool that will require the easiest/lightest customization - it will be cheaper than trying to get a tool for free and using a small team to massively customize it.
A tear just left my eye.
So many people think this is easy and won't pay for the expertise to hire "the best" (Everyone wants the best, everyone also wants to pay industry average wages... Moneyball doesn't work in Tech). A good recruiter will be able to talk to you to find what you are looking for, find you a couple candidates - listen to you on why you didn't like them and change what they are sending to you, repeat until you find what you are looking for
Honestly it sounds like you have a specific set of filters you are looking for that you haven't applied (cryptographic systems, security maybe) and are bringing in generic candidates that weren't screened for these skills. I can trivially answer your questions - but then I have been in that area for 20 years, don't ask me how to write a database query or setup a JSON parser.
(And they're quite convinced they're right)
They say the oaks are just too lofty
And they grab up all the light
But the oaks can't help their feelings
If they like the way they're made
And they wonder why the maples
Can't be happy in their shade
And of course the sad ending
So the maples formed a union
And demanded equal rights
'The oaks are just too greedy
We will make them give us light'
Now there's no more oak oppression
For they passed a noble law
And the trees are all kept equal
By hatchet, axe and saw
--- Rush 1978
Remember, you can never make yourself better by having someone else chop the other person down. Very powerful song - still resonates today.
If my preferred college has 100 openings there is a finite number of successes (people allowed in). If I allow people who aren't as qualified as I am into the college, and I don't make it in because I am not a particular color, sex, sexuality, etc. then I have been pushed back and must go to a less desirable college. This is happening today in MANY college admissions (with colleges being sued because they continue to discriminate on the grounds of sex and race/ethnicity).
Now lets throw in other factors where sex and race are used to determine winners and losers and it is demonstrably provable that for every person you push forward, you must push another person back.
If you believe a rising tide raises all boats are you a firm believer in trickle down economics as well?
I am not talking about adding an MPLS tag that gets inserted on insertion into the provider and stripped before it leaves the other side, I am talking adjusting my traffic to add content to the L4+ content. The ISP should only adjust things at L3 and below. Everything above that should never be touched (Ok - Large scale NAT I can live with - Lets move that to L5+)
Airfare is driven off of the cheapest flight between two places - saving a couple hours isn't going to be a commercial success, look at the example of the Concorde.
Once an animal is taken out of the wild and held in captivity it is almost impossible to put them back into the wild - they just can't survive. This is why you are very careful with taking animals out of the wild - it is a one way street.
Got to love people's plans - Of course there is nothing stopping him from being hit by a bus, or other random thing that can get people.