Peerio. ಠ_ಠ Disapproval Look. Evidence Based Scheduling. Evidence Based Scheduling by Joel Spolsky Friday, October 26, 2007 Software developers don’t really like to make schedules. Usually, they try to get away without one. “It’ll be done when it’s done!” Most of the schedules you do see are halfhearted attempts. Hilarious! You want to be spending your time on things that get the most bang for the buck. Why won’t developers make schedules? Over the last year or so at Fog Creek we’ve been developing a system that’s so easy even our grouchiest developers are willing to go along with it. The steeper the curve, the more confident you are that the ship date is real.
Here’s how you do it. 1) Break ‘er down When I see a schedule measured in days, or even weeks, I know it’s not going to work. This forces you to actually figure out what you are going to do. If you are sloppy, and pick big three-week tasks (e.g., “Implement Ajax photo editor”), then you haven’t thought about what you are going to do. 2) Track elapsed time You can’t, really. Anyway. Summary. Why Scrum Should Basically Just Die In A Fire. Conversations with Panda Strike CEO Dan Yoder inspired this blog post. Consider story points. If you're not familiar with Scrum, here's how they work: you play a game called "Planning Poker," where somebody calls out a task, and then counts down from three to one.
On one, the engineers hold up a card with the number of "story points" which represents the relative cost they estimate for performing the task. So, for example, a project manager might say "integrating our login system with OpenAuth and Bitcoin," and you might put up the number 20, because it's the maximum allowable value. Wikipedia describes the goal of this game: The reason to use Planning Poker is to avoid the influence of the other participants. I have literally never seen Planning Poker performed in a way which fails to undermine this goal. Wikipedia gives the alleged structure of this process: In fairness to everybody who's tried this process and seen it fail, how could it not devolve? And you never will. Please buy it. Why? Abstract Wallpapers and Backgrounds - Page 689 - Desktop Nexus.
Discover Movies by Genre. HoaxBuster - Vérifier l'information en circulation sur le web. The Internet map. The map of the Internet Like any other map, The Internet map is a scheme displaying objects’ relative position; but unlike real maps (e.g. the map of the Earth) or virtual maps (e.g. the map of Mordor), the objects shown on it are not aligned on a surface.
Mathematically speaking, The Internet map is a bi-dimensional presentation of links between websites on the Internet. Every site is a circle on the map, and its size is determined by website traffic, the larger the amount of traffic, the bigger the circle. Users’ switching between websites forms links, and the stronger the link, the closer the websites tend to arrange themselves to each other. Charges and springs To draw an analogy from classical physics, one may say that websites are electrically charged bodies, while links between them are springs. Also, an analogy can be drawn from quantum physics. Anyway, the real algorithm of plotting The Internet map is quite far from the analogies given above.
Semantic web The Internet Phenomenon. 419 Eater - The largest scambaiting community on the planet! Joel on Software. The App I Used to Break Into My Neighbor’s Home | Threat Level. When I broke into my neighbor’s home earlier this week, I didn’t use any cat burglar skills. I don’t know how to pick locks. I’m not even sure how to use a crowbar. It turns out all anyone needs to invade a friend’s apartment is an off switch for their conscience and an iPhone. This was done politely: I even warned him the day before. Less than an hour later, I owned a key to his front door. What I didn’t tell my neighbor was that I spent about 30 seconds in the stairwell scanning his keys with software that would let me reproduce them with no specialized skills whatsoever.
Parking valets suddenly require a ludicrous level of trust. I copied my neighbor’s keys at a KeyMe kiosk about a mile from his house, inside a Rite Aid drugstore. Unintended Consequences A KeyMe kiosk shown in the company’s marketing materials. KeyMe Such services also enable jerks like me to steal your keys any time they get a moment alone with them. Even if KeyMe did help the cops, Marsh’s logic is somewhat flawed. Excuses For Lazy Coders. VirusTotal - Free Online Virus, Malware and URL Scanner. Programming Sucks. Every friend I have with a job that involves picking up something heavier than a laptop more than twice a week eventually finds a way to slip something like this into conversation: "Bro, you don't work hard. I just worked a 4700-hour week digging a tunnel under Mordor with a screwdriver. " They have a point. Mordor sucks, and it's certainly more physically taxing to dig a tunnel than poke at a keyboard unless you're an ant.
But, for the sake of the argument, can we agree that stress and insanity are bad things? All programming teams are constructed by and of crazy people Imagine joining an engineering team. Would you drive across this bridge? All code is bad Every programmer occasionally, when nobody's home, turns off the lights, pours a glass of scotch, puts on some light German electronica, and opens up a file on their computer.
This file is Good Code. Every programmer starts out writing some perfect little snowflake like this. There will always be darkness "Double you tee eff? " Ook. Terms of Service; Didn't Read. The Iceberg Secret, Revealed. By Joel Spolsky Wednesday, February 13, 2002 "I don't know what's wrong with my development team," the CEO thinks to himself. "Things were going so well when we started this project. For the first couple of weeks, the team cranked like crazy and got a great prototype working.
But since then, things seem to have slowed to a crawl. They're just not working hard any more. " Meanwhile, of course, the development team has no idea that anything's wrong. Don't let this happen to you! It's pretty clear that programmers think in one language, and MBAs think in another. Since I started working in the software industry, almost all the software I've worked on has been what might be called "speculative" software. Have you ever noticed that on these custom projects, the single most common cause of overruns, failures, and general miserableness always boils down to, basically, "the (insert expletive here) customer didn't know what they wanted?
" Here are three versions of the same pathology: Discuss Next: Desktop Nexus Wallpapers - Background Images, Wallpaper, Desktop Wallpapers, Computer Backgrounds. HoaxBuster - Vérifier l'information en circulation sur le web. Urban Legends.