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

 



Forgot your password?
typodupeerror
×

Comment Re:You don't. (Score 3, Interesting) 208

This story has a lot of valuable lessons to be learned. The first lesson, I think, that you can take from your experience is that you are wholly unqualified to deal with the political and management issues involved. Therefore, do not involve yourself in management or politics. The (non-technical) suggestions given have all involved either an upward appeal to authority, or coercive measures. These will only make matters worse for you. If you want to keep your job, and think that you actually have a chance to make things work, ingratiate yourself to some people who can support you if things go south. I doubt very much that you are being deliberately set up as a fall guy. The school, after all, has a need to stay somewhat technologically relevant, but they're doing it on increasingly less money.

I'm guessing you went into education because you want to make a difference. Some people I know did as well, and they all tell the same story. Long, hard hours with very little acknowledgement. I would guess that's a reality of education these days. With a budget that's always short on funds, management will squeeze every last drop of effort from every employee. So, work under the assumption that the people who hold the purse strings are under at least as much pressure as you are. Maybe it's not true, but there's nothing you can do about it except quit.

Off the top of my head, the best people to get on your side are teachers and students. While you can't solve everything all at once, perhaps there are some small problems you can solve for specific people. And, while someone joked about making network maintenance an elective, there's probably some truth to it. I volunteered to help out the sole network admin when I was in high school. Perhaps some bright students would be willing to help out in exchange for some tutoring. The important thing is that some people know who you are and what you do, and can commiserate since your job is just as difficult as theirs. If it's important to you, hang in there. If it's not, then it's probably time to look for something less stressful.

Biotech

Commercial, USB-Powered DNA Sequencer Coming This Year 95

Zothecula writes "Oxford Nanopore has been developing a disruptive nanopore-based technology for sequencing DNA, RNA, proteins, and other long-chain molecules since its birth in 2005. The company has just announced that within the next 6-9 months it will bring to market a fast, portable, and disposable protein sequencer that will democratize sequencing by eliminating large capital costs associated with equipment required to enter the field."

Comment Re:design document vs. documenting source code? (Score 1) 545

I used to lean toward the second camp, but now I lean toward the first camp :)

Glad to hear it. I'm the first to admit that I don't always document well enough, but I'm a build-it-then-fix-it kind of guy. I've been at it long enough to get an extensible architecture off the ground right away. I'd work better with someone that's a get-it-right-the-first-time kind of guy telling me what I'm doing wrong, though.

Comment Re:Measuring readability (Score 1) 545

The developer can add comments, or rename variables, or restructure the code to make it clearer, but the end result should be readable code with fewer bugs (bugs live in hard-to-understand code, simply adding some intermediate variables to a complex formula can make them go away)

"Don't get suckered by the comments -- they can be terribly misleading. Debug only code." -- Dave Storer

This is why I always add my documentation at the end. A good programmer knows how to use his debugger. Properly named variables and methods will allow you to step through a program until you understand how it works. Once your understanding is clear, and you are quite certain that the code is good enough for somebody else, add enough documentation to aid other programmers in using or maintaining your code. The only way to know how much is needed is through the code review. The only exception I can think of to this process is when releasing the source code to the general public or to a client for their own maintenance. Since you don't usually have a code review with them, it's best to go for overkill. A pain sometimes, but a necessary part of a complete product.

Comment Causal Link (Score 5, Informative) 341

The crux of the case will lie in proving that there is a causal link between the lack of laws requiring ISPs to block websites, and the damages claimed. The precedent is Francovich v. Italy. However, given that the judge in a ruling against British Telecom forcing them to use Cleanfeed to block access to websites like Newzbin and TPB acknowledge that tools to circumvent the system were available. And, in fact, Newzbin has released a client allowing access to their website despite the Cleanfeed block. The same software allows access to TPB. It relies on both encryption and the TOR network. Newzbin told BBC news that 93.5% of UK users have downloaded their Cleanfeed circumvention software. This flies in the face of the judge's comment that "Even assuming that they all have the ability to acquire [the means to circumvent Cleanfeed], it does not follow that they will all wish to expend the time and effort required."

93.5% of UK Newzbin users may not be "all" people in the UK who want to use file sharing networks, but it certainly means that establishing the causal link between lack of ISP blocking remedies and damages from file sharing will be difficult. People want access to those files, and Cleanfeed has proven largely ineffective at stopping two of the main sites involved in sharing. It should also be noted that these sites are not the actual hosters of the allegedly damaging files; they are merely portals to peer-to-peer networks that have other access methods available (e.g. DHT on BitTorrent). Again, the claim that blocking these websites would prevent financial damage is rather dubious.

Comment Re:Switched to Pathfinder? (Score 1) 309

I much prefer Pathfinder. 4th ed. removed too many things and made a single-page character sheet extremely difficult. I don't like the attempt to make D & D more "video-gamey". Our D & D group runs a Pathfinder/d20 Modern mix that's quite enjoyable. I have no intention of moving away from 3.5-compatible source material (just like the 1st ed. people have no need of moving away from the one they learned.)

Comment Re:It's a hassle, but a tiny one... (Score 2) 142

I suspect we'll take the coward's way out and shut down processing for a minute before until a minute after and resync the clocks in the interim.

This was how I figured transaction processing would be handled. It sucks that you have to pay high-priced consultants to get that answer; plenty of people would give it to you for free.

That will, of course, be charged to our SLA downtime

I didn't consider this aspect. Thinking about it makes me realize just how stupid a leap second is. A lot of transaction processing requires >99.999% uptime, and even that two minutes (assuming everything goes perfectly smoothly) is expensive. Couldn't they be accumulated and have an extra leap year once every 86400 years?

Slashdot Top Deals

"Look! There! Evil!.. pure and simple, total evil from the Eighth Dimension!" -- Buckaroo Banzai

Working...