Software Project Quotes

Adding manpower to a late software project, makes it later.

The bearing of a child takes nine months, no matter how many women are assigned.

Broadly speaking, the human brain is a collection of software hacks compiled into a single, somehow-functional unit. Each “feature” was added as a random mutation that solved some specific problem to increase our odds of survival. In short, the human brain is a mess.

Software projects can be thought of as having two distinct stages: figuring out what to build (build the right product), and building it (building the product right). The first stage is dominated by product discovery, and the second stage is all about execution.

Programming is about managing complexity: the complexity of the problem, laid upon the complexity of the machine. Because of this complexity, most of our programming projects fail.

Adding manpower to a late software project makes it later.

We sort of understood abstractly the idea that there are only two kinds of software projects: failures and future legacy horrors.

The business we're in is more sociological than technological, more dependent on workers' abilities to communicate with each other than their abilities to communicate with machines.

The conclusion is simple: if a 200-man project has 25 managers who are the most competent and experienced programmers, fire the 175 troops and put the managers back to programming.

The fundamental assumption underlying all software projects is that software is easy to change. If you violate this assumption by creating inflexible structures, then you undercut the economic model that the entire industry is based on. In

In software development there’s a term called “Brooks’s Law” that Fred Brooks first coined back in 1975 in his seminal book The Mythical Man-Month. Put simply, Brooks’s Law says “adding manpower to a late software project makes it later.”8 This has been borne out in study after study.

Any software project must have a technical leader, who is responsible for all technical decisions made by the team and have enough authority to make them. Responsibility and authority are two mandatory components that must be present in order to make it possible to call such a person an architect.

They took one look at Zip2’s code and began rewriting the vast majority of the software. Musk bristled at some of their changes, but the computer scientists needed just a fraction of the lines of code that Musk used to get their jobs done. They had a knack for dividing software projects into chunks that could be altered and refined whereas Musk fell into the classic self-taught coder trap of writing what developers call hairballs—big, monolithic hunks of code that could go berserk for mysterious reasons.

One study found that in more than 85% of the open source projects the researchers examined on GitHub, less than 5% of developers were responsible for over 95% of code and social interactions.7

At first I hoped that such a technically unsound project would collapse but I soon realized it was doomed to success. Almost anything in software can be implemented, sold, and even used given enough determination. There is nothing a mere scientist can say that will stand against the flood of a hundred million dollars. But there is one quality that cannot be purchased in this way - and that is reliability. The price of reliability is the pursuit of the utmost simplicity. It is a price which the very rich find most hard to pay.

The only way to reduce the variability in the estimate is to reduce the variability in the project.

Building a project should be a single trivial operation.

Bus factor (noun): the number of people that need to get hit by a bus before your project is completely doomed.

Andy Weir built a career as a software engineer until the success of his first published novel, The Martian,

IBM veteran and computer science professor Frederick Brooks argued that adding manpower to complex software projects actually delayed progress.

one of the quirkier cognitive disorders to which software project management is prone.

More software projects have gone awry for lack of calendar time than for all other causes combined.

Many rookie software managers think that they can "motivate" their programmers to work faster by giving them nice, "tight" (unrealistically short) schedules. I think this kind of motivation is brain-dead. When I'm behind schedule, I feel doomed and depressed and unmotivated. When I'm working ahead of schedule, I'm cheerful and productive. The schedule is not the place to play psychological games.

Geeks are not the world’s rowdiest people. We’re quiet and introspective, and usually more comfortable communing with our keyboards or a good book than each other. Our idea of how to paint the Emerald City red involves light liquor, heavy munchies, and marathon sessions of video games of the ‘giant robots shooting each other and everything else in sight’ variety. We debate competing lines of software or gaming consoles with passion, and dissect every movie, television show, and novel in the science fiction, fantasy, and horror genres. With as many of us as there are in this town, people inevitably find ways to cater to us when we get in the mood to spend our hard-earned dollars. Downtown Seattle boasts grandiose geek magnets, like the Experience Music Project and the Experience Science Fiction museum, but it has much humbler and far more obscure attractions too, like the place we all went to for our ship party that evening: a hole-in-the-wall bar called the Electric Penguin on Capitol Hill.

As Thomas Hobbes observed in the 17th century, life under mob rule is solitary, poor, nasty, brutish and short. Life on a poorly run software project is solitary, poor, nasty, brutish, and hardly ever short enough.

It’s still unmessed-with country. You like to think it goes on forever, but the colonisers are coming. The suits and tenderfeet. You can hear the blue-eyed-soul music over the ridgeline. There’s already a half dozen well-funded projects for designing software to crawl the Deep Web –” “Is that,” Maxine wonders, “like, ‘Ride the Wild Surf’?” “Except summer will end all too soon, once they get down here, everything’ll be suburbanised faster than you can say ‘late capitalism.’ Then it’ll be just like up there in the shallows. Link by link, they’ll bring it all under control, safe and respectable. Churches on every corner. Licenses in all the saloons. Anybody still wants his freedom’ll have to saddle up and head somewhere else.

The majority of the cost of a software project is in long-term maintenance. In order to minimize the potential for defects as we introduce change, it’s critical for us to be able to understand what a system does. As systems become more complex, they take more and more time for a developer to understand, and there is an ever greater opportunity for a misunderstanding. Therefore, code should clearly express the intent of its author. The clearer the author can make the code, the less time others will have to spend understanding it. This will reduce defects and shrink the cost of maintenance.

Businesses frequently prioritize new feature releases over fixing technical debt. They choose to work on revenue-generating work instead of revenue-protection work. This rarely works out as the business hopes, particularly as problems discovered during the final stages of uncompleted projects drag engineers away from the newer projects.

Risk management is not the same as worrying about your project.

incremental development can be disconcerting for teams and management who aren’t used to it because it front-loads the stress in a project.

Kanban is not a software development lifecycle methodology or an approach to project management.

Broadly speaking, the human brain is a collection of software hacks compiled into a single, somehow-functional unit.

Good ideas kill projects. Sometimes it's a quick death, but often it's a slow, lingering death caused by missed milestones and a spiraling bug count.

The number of months of a project depends upon its sequential constraints. The maximum number of men depends upon the number of independent subtasks.

most software- or systems-development projects start out without a context diagram, blissfully unaware that they need one.

Just by making the architect role explicit, a team can effectively resolve many technical conflicts.

How does a project get to be a year late? . . . . One day at a time.

It is not enough for code to work. Code that works is often badly broken. Programmers who satisfy themselves with merely working code are behaving unprofessionally. They may fear that they don’t have time to improve the structure and design of their code, but I disagree. Nothing has a more profound and long-term degrading effect upon a development project than bad code.

As for relegated/delegated responsibility to ensure organizational software licensing compliance, management is still accountable when intellectual property rights are violated. If the safeguarding responsibility is assigned to an ineffective and/or inefficient unit within an organization, IT audit should recommend an alternative arrangement after the risks are substantiated.

The statistics about reading are particularly discouraging: The average software developer, for example, doesn’t own a single book on the subject of his or her work, and hasn’t ever read one.

The approach to digital culture I abhor would indeed turn all the world's books into one book, just as Kevin (Kelly) suggested. It might start to happen in the next decade or so. Google and other companies are scanning library books into the cloud in a massive Manhattan Project of cultural digitization. What happens next is what's important. If the books in the cloud are accessed via user interfaces that encourage mashups of fragments that obscure the context and authorship of each fragment, there will be only one book. This is what happens today with a lot of content; often you don't know where a quoted fragment from a news story came from, who wrote a comment, or who shot a video. A continuation of the present trend will make us like various medieval religious empires, or like North Korea, a society with a single book. The Bible can serve as a prototypical example. Like Wikipedia, the Bible's authorship was shared, largely anonymous, and cumulative, and the obscurity of the individual authors served to create an oracle-like ambience for the document as "the literal word of God." If we take a non-metaphysical view of the Bible, it serves as a link to our ancestors, a window. The ethereal, digital replacement technology for the printing press happens to have come of age in a time when the unfortunate ideology I'm criticizing dominates technological culture. Authorship - the very idea of the individual point of view - is not a priority of the new ideology. The digital flattening of expression into a global mush is not presently enforced from the top down, as it is in the case of a North Korean printing press. Instead, the design of software builds the ideology into those actions that are the easiest to perform on the software designs that are becoming ubiquitous. It is true that by using these tools, individuals can author books or blogs or whatever, but people are encouraged by the economics of free content, crowd dynamics, and lord aggregators to serve up fragments instead of considered whole expressions or arguments. The efforts of authors are appreciated in a manner that erases the boundaries between them. The one collective book will absolutely not be the same thing as the library of books by individuals it is bankrupting. Some believe it will be better; others, including me, believe it will be disastrously worse. As the famous line goes from Inherit the Wind: 'The Bible is a book... but it is not the only book' Any singular, exclusive book, even the collective one accumulating in the cloud, will become a cruel book if it is the only one available.

It is not too bold a statement to say that a software development project is one of the riskiest investments a business makes. For example, the chance of a large software project being canceled increases with project duration. In the 1990s, those projects that exceeded two years of elapsed calendar time in development had a default rate that exceeded the worst rated junk bonds (something over 25%).

Democracy is a continuous, open process of civility. A democracy can never be “done”; updating democracy can never be over. Democracy can be nothing else but a continuous process, because we use it to organize our life, and life is nothing but a continuous process. Democracy can be compared to an operating system or an anti-virus software; if it does not get perpetually updated, it becomes obsolete very fast. Trusting the updates or the “improvements” of democracy to the elected and the owned mass media is like trusting the updates of an anti-virus program to virus creators; it defeats the purpose of updates or improvements.

Especially noteworthy is his comment that new people added late in a development project must be team players willing to pitch in and work within the process, and not attempt to alter or improve the process itself!

Kanban is not a software development lifecycle methodology or an approach to project management. It requires that some process is already in place so that Kanban can be applied to incrementally change the underlying process.

Broadly speaking, the human brain is a collection of software hacks compiled into a single, somehow-functional unit. Each “feature” was added as a random mutation that solved some specific problem to increase our odds of survival.

The key is to take a larger project or goal and break it down into smaller problems to be solved, constraining the scope of work to solving a key problem, and then another key problem. This strategy, of breaking a project down into discrete, relatively small problems to be resolved, is what Bing Gordon, a cofounder and the former chief creative officer of the video game company Electronic Arts, calls smallifying. Now a partner at the venture capital firm Kleiner Perkins, Gordon has deep experience leading and working with software development teams. He’s also currently on the board of directors of Amazon and Zynga. At Electronic Arts, Gordon found that when software teams worked on longer-term projects, they were inefficient and took unnecessary paths. However, when job tasks were broken down into particular problems to be solved, which were manageable and could be tackled within one or two weeks, developers were more creative and effective.

Where technology acquisition was once the province of the CIO, today it’s the practitioner leading that process, because by the time a CIO typically hears about a project today, a majority of the technology and architectural decisions have already been made.

Kanban must not be thought of as a software development lifecycle process or a project-management process. Kanban is a change-management technique that requires making alterations to an existing process: changes such as adding work-in-progress limits to it. Work

Recommended Reading The Definitive Guide to Getting Your Budget Approved by Johannes Ritter and Frank Röttgers provides a systematic guide for creating a financial business case. The book includes examples as well as the methods for using Monte Carlo simulation and sensitivity analysis to create the business case. The methods described in the book can also be used for quantifying risks and project costs. Mary and Tom Poppendieck in their book Lean Software Development: describe the lean principles and the types of waste in software projects.

Nothing has a more profound and long-term degrading effect upon a development project than bad code. Bad schedules can be redone, bad requirements can be redefined. Bad team dynamics can be repaired. But bad code rots and ferments, becoming an inexorable weight that drags the team down.

agile development reflects a product lifecycle approach (continuous delivery of value), rather than a project approach (begin-end). While an individual release of a product can be managed as a project, an agile approach views a release as a single stage in a product’s ongoing evolution.

Broadly speaking, the human brain is a collection of software hacks compiled into a single, somehow-functional unit. Each “feature” was added as a random mutation that solved some specific problem to increase our odds of survival. In short, the human brain is a mess. Everything about evolution is messy.

Managers of programming projects aren’t always aware that certain programming issues are matters of religion. If you’re a manager and you try to require compliance with certain programming practices, you’re inviting your programmers’ ire. Here’s a list of religious issues: ■ Programming language ■ Indentation style ■ Placing of braces ■ Choice of IDE ■ Commenting style ■ Efficiency vs. readability tradeoffs ■ Choice of methodology—for example, Scrum vs. Extreme Programming vs. evolutionary delivery ■ Programming utilities ■ Naming conventions ■ Use of gotos ■ Use of global variables ■ Measurements, especially productivity measures such as lines of code per day

The moral is this: do not underestimate the power of playing the social game. It’s not about tricking or manipulating people; it’s about creating relationships to get things done. Relationships always outlast projects. When you’ve got richer relationships with your coworkers, they’ll be more willing to go the extra mile when you need them.

the modern relationship between software and hardware is essentially the same as that between music and the instrument or voice that brings it to life. A single computer can transform itself into the cockpit of a fighter jet, a budget projection, a chapter of a novel, or whatever else you want, just as a single piano can be used to play Bach or funky blues.

Organizations that manage IT delivery as projects instead of products are using managerial principles from two ages ago and cannot expect those approaches to be adequate for succeeding in this one. Visionary organizations are creating and managing their Value Stream Networks and product portfolios in order to leapfrog their competition in the Age of Software

There was no escape: The entire Elliott 503 Mark II software project had to be abandoned, and with it, over thirty man-years of programming effort, equivalent to nearly one man’s active working life, and I was responsible, both as designer and as manager, for wasting it. ... How did we recover from the catastrophe? First, we classified our 503 customers into groups, according to the nature and size of the hardware configurations which they had bought ... We assigned to each group of customers a small team of programmers and told the team leader to visit the customers to find out what they wanted; to select the easiest request to fulfill, and to make plans (but no promises) to implement it. In no case would we consider a request for a feature that would take more than three months to implement and deliver. The project leader would then have to convince me that the customers’ request was reasonable, that the design of the new feature was appropriate, and that the plans and schedules for implementation were realistic. Above all, I did not allow anything to be done which I did not myself understand. It worked! The software requested began to be delivered on the promised dates. With an increase in our confidence and that of our customers, we were able to undertake fulfilling slightly more ambitious requests. Within a year we had recovered from the disaster. Within two years, we even had some moderately satisfied customers.

Other benefits: As a company Adobe struggled for many years with people using pirated copies of its software, particularly for costly Creative Cloud applications like Photoshop. The subscription model automatically reduces piracy, since the company no longer ships packaged software that can be copied. Further, organizations on tight budgets with single projects can pay to use the service for only a month or two.

I would compare a project with a country, which is either properly regulated by the laws or enslaved by a dictator whom everybody is supposed to love. What modern management is doing in most companies is the latter scenario. They expect us to love the customer and work just because of that. There are no laws, no discipline, no regulations, and no principle, because, like every dictator, they simply are not competent enough in creating them. Dictators just capture the power and rule by the force: it's much easier than building a system of laws, which will work by itself. The management in software projects also can't create a proper management system, since they simply don't have enough knowledge for that. Instead, they expect our love. Isn't it obvious that rather soon that love turns into hate and we quit or the project collapses?

The bigger your project becomes, the harder it is to keep the innovation you had in the beginning of your project. Suddenly you have to consider hundreds of different use-cases . . . . Once you pass a few thousand active users, you’ll notice that helping your users takes more time than actually working on your project. People submit all kinds of issues, most of them aren’t actually issues, but feature requests or questions.84

You’re either remarkable or invisible,” says Seth Godin in his 2002 bestseller, Purple Cow.1 As he elaborated in a Fast Company manifesto he published on the subject: “The world is full of boring stuff—brown cows—which is why so few people pay attention…. A purple cow… now that would stand out. Remarkable marketing is the art of building things worth noticing.”2 When Giles read Godin’s book, he had an epiphany: For his mission to build a sustainable career, it had to produce purple cows, the type of remarkable projects that compel people to spread the word. But this left him with a second question: In the world of computer programming, where does one launch remarkable projects? He found his second answer in a 2005 career guide with a quirky title: My Job Went to India: 52 Ways to Save Your Job.3 The book was written by Chad Fowler, a well-known Ruby programmer who also dabbles in career advice for software developers.

The behavior of retailers when a vendor folds is very revealing. It tells us that they know something the vendors don’t. What they know is this: the price a consumer will pay is effectively capped by the expected future value of vendor service (where “service” is here construed broadly to include enhancements, upgrades, and follow-on projects). In other words, software is largely a service industry operating under the persistent but unfounded delusion that it is a manufacturing industry.

Denise: "So your present project is ready to pass to the testing people?" Ralph: "Absolutely." Denise: "Okay, since you're so sure it's adequately tested, I'm going to make you the following generous offer: If fewer than three bugs turn up in your component during testing, I will give you a raise. But if three or more bugs turn up during testing, you won't earn a raise this year." Ralph: "Um . . ." Denise: "Um what?" "Could I just have the component back for a few little tests I want to do?

Project managers don’t write code, they don’t test the use cases, and they’re not designing the interface. You know what a good project manager does? They are chaos-destroying machines, and each new person you bring onto your team, each dependency you create, adds hard-to-measure entropy to your team. A good project manager thrives on measuring, controlling, and crushing entropy. You did this easily when you were a team of five, but if you’re going to succeed at 105, what was done organically now needs to be done mechanically.

When people look under the hood, we want them to be impressed with the neatness, consistency, and attention to detail that they perceive. We want them to be struck by the orderliness. We want their eyebrows to rise as they scroll through the modules. We want them to perceive that professionals have been at work. If instead they see a scrambled mass of code that looks like it was written by a bevy of drunken sailors, then they are likely to conclude that the same inattention to detail pervades every other aspect of the project.

Life of a software engineer sucks big time during project release. Every single team member contribution is very important. At times, we have to skip breakfast, lunch and even dinner, just to make sure the given ‘TASK’ is completed. Worst thing, that’s the time we get to hear wonderful F* words. It can be on conference calls or on emails, still we have to focus and deliver the end product to a client, without any compromise on quality. Actually, every techie should be saluted. We are the reason for the evolution of Information Technology. We innovate. We love artificial intelligence. We create bots and much more. We take you closer to books. Touch and feel it without the need of carrying a paperback. We created eBook and eBook reader app: it’s basically a code of a software engineer that process the file, keeps up-to-date of your reading history, and gives you a smoother reading experience. We are amazing people. We are more than a saint of those days. Next time, when you meet a software engineer, thank him/her for whatever code he/she developed, tested, designed or whatever he/she did!

Some people mistakenly refer to software defects as bugs. When called bugs, they seem like pesky things that should be swatted or even ignored. This trivializes a critical problem and fosters a wrong attitude. Thus, when an engineer says there are only a few bugs left in a program, the reaction is one of relief. *Supposed, however, that we called them time bombs instead of bugs.* Would you feel the same sense of relief if a programmer told you that he had thoroughly tested a program and there were only a few time bombs left in it? Just using a different term changes your attitude entirely.

Or, suppose you want to motivate your managers to ship products on time, so you conspicuously promote each manager whose product goes out the door on schedule. All goes as planned until the situation arises in which one of your managers has a project where the testers are reporting numerous problems. Because managers who have shipped products on time have been promoted, this manager thinks, I want that promotion so I need to ship this on time, but those bug reports are getting in the way. I know what I'll do! I'll put the testers on another project until the developers have a chance to catch up.

Because I don’t have time for this bullshit,” she said. “We are building a ship to literally save our species. And we have very little time to get it done. It will have three astronauts—just three—to do experiments we can’t even conceive of now. We need them to be prepared for any possible line of study they deem necessary. So we are giving them everything. The collected knowledge of humankind, along with all software. Some of it is stupid. They probably won’t need Minesweeper for Windows 3.1, and they probably don’t need an unabridged Sanskrit-to-English dictionary, but they’re going to have them.

As test documentation goes, test plans have the briefest actual lifespan of any test artifact. Early in a project, there is a push to write a test plan [...]. Indeed, there is often an insistence among project managers that a test plan must exist and that writing it is a milestone of some importance. But, once such a plan is written, it is often hard to get any of those same managers to take reviewing and updating it seriously. The test plan becomes a beloved stuffed animal in the hands of a distracted child. We want it to be there at all times. We drag it around from place to place without ever giving it any real attention. We only scream when it gets taken away.

According to Petroski, real knowledge from real failure is the most powerful source of progress we have, provided we have the courage to carefully examine what happened. Perhaps this is why The Boeing Company, one of the largest airplane design and engineering firms in the world, keeps a black book of lessons it has learned from design and engineering failures.[4] Boeing has kept this document since the company was formed, and it uses it to help modern designers learn from past attempts. Any organization that manages to do this not only increases its chances for successful projects, but also helps create an environment that can discuss and confront failure openly, instead of denying and hiding from it. It seems that software developers need to keep black books of their own.

Rich Purnell sipped coffee in the silent building. Only his cubicle illuminated the otherwise dark room. Continuing with his computations, he ran a final test on the software he'd written. It passed. With a relieved sigh, he sank back in his chair. Checking the clock on his computer, he shook his head. 3:42am. Being an astrodynamicist, Rich rarely had to work late. His job was the find the exact orbits and course corrections needed for any given mission. Usually, it was one of the first parts of a project; all the other steps being based on the orbit. But this time, things were reversed. Iris needed an orbital path, and nobody knew when it would launch. A non-Hoffman Mars-transfer isn't challenging, but it does require the exact locations of Earth and Mars. Planets move as time goes by. An orbit calculated for a specific launch date will work only for that date. Even a single day's difference would result in missing Mars entirely. So Rich had to calculate many orbits. He had a range of 25 days during which Iris might launch. He calculated one orbital path for each. He began an email to his boss. "Mike", he typed, "Attached are the orbital paths for Iris, in 1-day increments. We should start peer-review and vetting so they can be officially accepted. And you were right, I was here almost all night. It wasn't that bad. Nowhere near the pain of calculating orbits for Hermes. I know you get bored when I go in to the math, so I'll summarize: The small, constant thrust of Hermes's ion drives is much harder to deal with than the large point-thrusts of presupply probes. All 25 of the orbits take 349 days, and vary only slightly in thrust duration and angle. The fuel requirement is nearly identical for the orbits and is well within the capacity of EagleEye's booster. It's too bad. Earth and Mars are really badly positioned. Heck, it's almost easier to-" He stopped typing. Furrowing his brow, he stared in to the distance. "Hmm." he said. Grabbing his coffee cup, he went to the break room for a refill. ... "Rich", said Mike. Rich Purnell concentrated on his computer screen. His cubicle was a landfill of printouts, charts, and reference books. Empty coffee cups rested on every surface; take-out packaging littered the ground. "Rich", Mike said, more forcefully. Rich looked up. "Yeah?" "What the hell are you doing?" "Just a little side project. Something I wanted to check up on." "Well... that's fine, I guess", Mike said, "but you need to do your assigned work first. I asked for those satellite adjustments two weeks ago and you still haven't done them." "I need some supercomputer time." Rich said. "You need supercomputer time to calculate routine satellite adjustments?" "No, it's for this other thing I'm working on", Rich said. "Rich, seriously. You have to do your job." Rich thought for a moment. "Would now be a good time for a vacation?" He asked. Mike sighed. "You know what, Rich? I think now would be an ideal time for you to take a vacation." "Great!" Rich smiled. "I'll start right now." "Sure", Mike said. "Go on home. Get some rest." "Oh, I'm not going home", said Rich, returning to his calculations. Mike rubbed his eyes. "Ok, whatever. About those satellite orbits...?" "I'm on vacation", Rich said without looking up. Mike shrugged and walked away.

Peopleware. A major contribution during recent years has been DeMarco and Lister's 1987 book, Peopleware: Productive Projects and Teams. Its underlying thesis is that "The major problems of our work are not so much technological as sociological in nature." It abounds with gems such as, "The manager's function is not to make people work, it is to make it possible for people to work." It deals with such mundane topics as space, furniture, team meals together. DeMarco and Lister provide real data from their Coding War Games that show stunning correlation between performances of programmers from the same organization, and between workplace characteristics and both productivity and defect levels. The top performers' space is quieter, more private, better protected against interruption, and there is more of it. . . . Does it really matter to you . . . whether quiet, space, and privacy help your current people to do better work or [alternatively] help you to attract and keep better people?[19]

When applying agile practices at the portfolio level, similar benefits accrue: • Demonstrable results—Every quarter or so products, or at least deployable pieces of products, are developed, implemented, tested, and accepted. Short projects deliver chunks of functionality incrementally. • Customer feedback—Each quarter product managers review results and provide feedback, and executives can view progress in terms of working products. • Better portfolio planning—Portfolio planning is more realistic because it is based on deployed whole or partial products. • Flexibility—Portfolios can be steered toward changing business goals and higher-value projects because changes are easy to incorporate at the end of each quarter. Because projects produce working products, partial value is captured rather than being lost completely as usually happens with serial projects that are terminated early. • Productivity—There is a hidden productivity improvement with agile methods from the work not done. Through constant negotiation, small projects are both eliminated and pared down.

The thing about Web companies is there's always something severely fucked-up. There is always an outage, always lost data, always compromised customer information, always a server going offline. You work with these clugey internal tools and patch together work-arounds to compensate for the half-assed, rushed development, and after a while the fucked-upness of the whole enterprise becomes the status quo. VPs insecure that they're not as in touch as they need to be with conditions on the ground insert themselves into projects midstream and you get serious scope creep. You present to the world this image that you're a buttoned-down tech company with everything in its right place but once you're on the other side of the firewall it looks like triage time in an emergency room, 24/7. Systems break down, laptops go into the blue screen of death, developers miskey a line of code, error messages appear that mean absolutely nothing. The instantaneousness with which you can fix stuff creates a culture that works by the seat of its pants. I swear the whole Web was built by virtue of developers fixing one mistake after another, constantly forced to compensate for the bugginess of their code.

One of those was Gary Bradski, an expert in machine vision at Intel Labs in Santa Clara. The company was the world’s largest chipmaker and had developed a manufacturing strategy called “copy exact,” a way of developing next-generation manufacturing techniques to make ever-smaller chips. Intel would develop a new technology at a prototype facility and then export that process to wherever it planned to produce the denser chips in volume. It was a system that required discipline, and Bradski was a bit of a “Wild Duck”—a term that IBM originally used to describe employees who refused to fly in formation—compared to typical engineers in Intel’s regimented semiconductor manufacturing culture. A refugee from the high-flying finance world of “quants” on the East Coast, Bradski arrived at Intel in 1996 and was forced to spend a year doing boring grunt work, like developing an image-processing software library for factory automation applications. After paying his dues, he was moved to the chipmaker’s research laboratory and started researching interesting projects. Bradski had grown up in Palo Alto before leaving to study physics and artificial intelligence at Berkeley and Boston University. He returned because he had been bitten by the Silicon Valley entrepreneurial bug.

Imagine a latter-day Helmholtz presented by an engineer with a digital camera, with its screen of tiny photocells, set up to capture images projected directly on to the surface of the screen. That makes good sense, and obviously each photocell has a wire connecting it to a computing device of some kind where images are collated. Makes sense again. Helmholtz wouldn’t send it back. But now, suppose I tell you that the eye’s ‘photocells’ are pointing backwards, away from the scene being looked at. The ‘wires’ connecting the photocells to the brain run all over the surface of the retina, so the light rays have to pass through a carpet of massed wires before they hit the photocells. That doesn’t make sense – and it gets even worse. One consequence of the photocells pointing backwards is that the wires that carry their data somehow have to pass through the retina and back to the brain. What they do, in the vertebrate eye, is all converge on a particular hole in the retina, where they dive through it. The hole filled with nerves is called the blind spot, because it is blind, but ‘spot’ is too flattering, for it is quite large, more like a blind patch, which again doesn’t actually inconvenience us much because of the ‘automatic Photoshop’ software in the brain. Once again, send it back, it’s not just bad design, it’s the design of a complete idiot.

Walking back through the mall to the exit nearest our part of the parking lot, we passed one shop which sold computers, printers, software, and games. It was packed with teenagers, the kind who wear wire rims and know what the new world is about. The clerks were indulgent, letting them program the computers. Two hundred yards away, near the six movie houses, a different kind of teenager shoved quarters into the space-war games, tensing over the triggers, releasing the eerie sounds of extraterrestrial combat. Any kid back in the computer store could have told the combatants that because there is no atmosphere in space, there is absolutely no sound at all. Perfect distribution: the future managers and the future managed ones. Twenty in the computer store, two hundred in the arcade. The future managers have run on past us into the thickets of CP/M, M-Basic, Cobal, Fortran, Z-80, Apples, and Worms. Soon the bosses of the microcomputer revolution will sell us preprogrammed units for each household which will provide entertainment, print out news, purvey mail-order goods, pay bills, balance accounts, keep track of expenses, and compute taxes. But by then the future managers will be over on the far side of the thickets, dealing with bubble memories, machines that design machines, projects so esoteric our pedestrian minds cannot comprehend them. It will be the biggest revolution of all, bigger than the wheel, bigger than Franklin’s kite, bigger than paper towels.

Over the span of a year or two, teams that were moving very fast at the beginning of a project can find themselves moving at a snail’s pace. Every change they make to the code breaks two or three other parts of the code. As productivity decreases, management does the only thing they can; they add more staff to the project to increase productivity. But that new staff is not versed in the design of the system. Furthermore, they, and everyone else on the team, are under horrific pressure to increase productivity. So they all make more and more messes, driving productivity further toward zero. Eventually the team rebels. They inform management that they cannot continue to develop in this odious code base. Management does not want to expend resources on a whole new redesign of the project, but they cannot deny that productivity is terrible. Eventually, they bend to the demands of the developers and authorize the grand redesign in the sky. A new tiger team is selected. Everyone wants to be on this team because it’s a green-field project. They get to start over and create something wonderful. But only the best and brightest are chosen for the tiger team. Everyone else must continue to maintain the current system. Now the two teams are in a race. The tiger team must build a new system that does everything that the old system does. Management will not replace the old system until the new system can do everything that the old system does. This race can go on for a very long time. I’ve seen it take 10 years. And by the time it’s done, the original members of the tiger team are long gone, and the current members are demanding that the new system be redesigned because it’s such a mess.

If you want to make money at some point, remember this, because this is one of the reasons startups win. Big companies want to decrease the standard deviation of design outcomes because they want to avoid disasters. But when you damp oscillations, you lose the high points as well as the low. This is not a problem for big companies, because they don't win by making great products. Big companies win by sucking less than other big companies.” - “The place to fight design wars is in new markets, where no one has yet managed to establish any fortifications. That's where you can win big by taking the bold approach to design, and having the same people both design and implement the product. Microsoft themselves did this at the start. So did Apple. And Hewlett- Packard. I suspect almost every successful startup has.” - “Great software, likewise, requires a fanatical devotion to beauty. If you look inside good software, you find that parts no one is ever supposed to see are beautiful too.” - “The right way to collaborate, I think, is to divide projects into sharply defined modules, each with a definite owner, and with interfaces between them that are as carefully designed and, if possible, as articulated as programming languages. Like painting, most software is intended for a human audience. And so hackers, like painters, must have empathy to do really great work. You have to be able to see things from the user's point of view.” - “It turns out that looking at things from other people's point of view is practically the secret of success.” - “Part of what software has to do is explain itself. So to write good software you have to understand how little users understand. They're going to walk up to the software with no preparation, and it had better do what they guess it will, because they're not going to read the manual.

Although thrilled that the era of the personal computer had arrived, he was afraid that he was going to miss the party. Slapping down seventy-five cents, he grabbed the issue and trotted through the slushy snow to the Harvard dorm room of Bill Gates, his high school buddy and fellow computer fanatic from Seattle, who had convinced him to drop out of college and move to Cambridge. “Hey, this thing is happening without us,” Allen declared. Gates began to rock back and forth, as he often did during moments of intensity. When he finished the article, he realized that Allen was right. For the next eight weeks, the two of them embarked on a frenzy of code writing that would change the nature of the computer business.1 Unlike the computer pioneers before him, Gates, who was born in 1955, had not grown up caring much about the hardware. He had never gotten his thrills by building Heathkit radios or soldering circuit boards. A high school physics teacher, annoyed by the arrogance Gates sometimes displayed while jockeying at the school’s timesharing terminal, had once assigned him the project of assembling a Radio Shack electronics kit. When Gates finally turned it in, the teacher recalled, “solder was dripping all over the back” and it didn’t work.2 For Gates, the magic of computers was not in their hardware circuits but in their software code. “We’re not hardware gurus, Paul,” he repeatedly pronounced whenever Allen proposed building a machine. “What we know is software.” Even his slightly older friend Allen, who had built shortwave radios, knew that the future belonged to the coders. “Hardware,” he admitted, “was not our area of expertise.”3 What Gates and Allen set out to do on that December day in 1974 when they first saw the Popular Electronics cover was to create the software for personal computers. More than that, they wanted to shift the balance in the emerging industry so that the hardware would become an interchangeable commodity, while those who created the operating system and application software would capture most of the profits.

Betsy didn’t want to be at the party any more than Cole did. She’d met the birthday girl in a spin class a couple of years earlier and had been declining her Evites ever since. In an effort to meet new people, however, this time Betsy replied “Yes.” She took a cab to the party, wondering why she was going at all. When Betsy met Cole there was a spark, but she was ambivalent. Cole was clearly smart and well educated, but he didn’t seem to be doing much about it. They had some nice dates, which seemed promising. Then, after sleeping over one night and watching Cole wake up at eleven a.m. and grab his skateboard, Betsy felt less bullish. She didn’t want to help another boyfriend grow up. What Betsy didn’t know was that, ever since he’d started spending time with her, Cole had regained some of his old drive. He saw the way she wanted to work on her sculptures even on the weekend, how she and her friends loved to get together to talk about their projects and their plans. As a result, Cole started to think more aspirationally. He eyed a posting for a good tech job at a high-profile start-up, but he felt his résumé was now too shabby to apply. As luck would have it—and it is often luck—Cole remembered that an old friend from high school, someone he bumped into about once every year or two, worked at the start-up. He got in touch, and this friend put in a good word to HR. After a handful of interviews with different people in the company, Cole was offered the position. The hiring manager told Cole he had been chosen for three reasons: His engineering degree suggested he knew how to work hard on technical projects, his personality seemed like a good fit for the team, and the twentysomething who vouched for him was well liked in the company. The rest, the manager said, Cole could learn on the job. This one break radically altered Cole’s career path. He learned software development at a dot-com on the leading edge. A few years later, he moved over and up as a director of development at another start-up because, by then, the identity capital he’d gained could speak for itself. Nearly ten years later, Cole and Betsy are married. She runs a gallery co-op. He’s a CIO. They have a happy life and gladly give much of the credit to Cole’s friend from high school and to the woman with the Evites.

How to choose a best website development company RNS IT Solutions is the best Software development company. When choosing a development company for your website, it is very important not only to look at the price, but also the quality of the work you hope to obtain and it is that a good Web of quality, realized of the hand of good engineers who have been working in the sector for years, can make you recover the investment in a short time and generate great benefits in the long term. Of course, to have a quality website the initial investment will probably be greater than you expect and maybe right now you think that the web you need does not require much quality, or a lot of work, but stop to think for a moment and consider the possibility that you are totally wrong, because that may depend on the future of your company as well as Web Development company India.The image that you want to transmit to the clients of the same one and the investment that you will have to do in the web once developed. With all this I do not mean that you have to ask for a loan from the bank to pay for the web. If the project you have in mind takes more work than you initially thought and the budget is out of your expectations, you can always limit and remove features that are dispensable. In this way you can publish the Web as soon as possible, so that once the initial investment is amortized, you can continue investing in adding those features that were left in the background. There are few Web Development Company In India hat right now could not survive, if they were not involved in the online world and it costs much less to make you a quality professional website, with a higher initial investment, to make you a website on which you have to invest, and then large amounts in development and consulting to correct deficiencies initially not contemplated. In the worst case, a bad development, may even force you to throw all the code of the web to the trash, to have to start from scratch. But what is quality of Web Development Services India? Let's see the characteristics that a website must have in order to be considered quality and professional: In any development project, meetings are always held to develop an initial analysis, gathering all the requirements and objectives of the web that the client wants. At this point you should have a proactive attitude, proposing functionalities that could be interesting or alternative ideas that we know can generate good results.

me to be honest about his failings as well as his strengths. She is one of the smartest and most grounded people I have ever met. “There are parts of his life and personality that are extremely messy, and that’s the truth,” she told me early on. “You shouldn’t whitewash it. He’s good at spin, but he also has a remarkable story, and I’d like to see that it’s all told truthfully.” I leave it to the reader to assess whether I have succeeded in this mission. I’m sure there are players in this drama who will remember some of the events differently or think that I sometimes got trapped in Jobs’s distortion field. As happened when I wrote a book about Henry Kissinger, which in some ways was good preparation for this project, I found that people had such strong positive and negative emotions about Jobs that the Rashomon effect was often evident. But I’ve done the best I can to balance conflicting accounts fairly and be transparent about the sources I used. This is a book about the roller-coaster life and searingly intense personality of a creative entrepreneur whose passion for perfection and ferocious drive revolutionized six industries: personal computers, animated movies, music, phones, tablet computing, and digital publishing. You might even add a seventh, retail stores, which Jobs did not quite revolutionize but did reimagine. In addition, he opened the way for a new market for digital content based on apps rather than just websites. Along the way he produced not only transforming products but also, on his second try, a lasting company, endowed with his DNA, that is filled with creative designers and daredevil engineers who could carry forward his vision. In August 2011, right before he stepped down as CEO, the enterprise he started in his parents’ garage became the world’s most valuable company. This is also, I hope, a book about innovation. At a time when the United States is seeking ways to sustain its innovative edge, and when societies around the world are trying to build creative digital-age economies, Jobs stands as the ultimate icon of inventiveness, imagination, and sustained innovation. He knew that the best way to create value in the twenty-first century was to connect creativity with technology, so he built a company where leaps of the imagination were combined with remarkable feats of engineering. He and his colleagues at Apple were able to think differently: They developed not merely modest product advances based on focus groups, but whole new devices and services that consumers did not yet know they needed. He was not a model boss or human being, tidily packaged for emulation. Driven by demons, he could drive those around him to fury and despair. But his personality and passions and products were all interrelated, just as Apple’s hardware and software tended to be, as if part of an integrated system. His tale is thus both instructive and cautionary, filled with lessons about innovation, character, leadership, and values.

A famous British writer is revealed to be the author of an obscure mystery novel. An immigrant is granted asylum when authorities verify he wrote anonymous articles critical of his home country. And a man is convicted of murder when he’s connected to messages painted at the crime scene. The common element in these seemingly disparate cases is “forensic linguistics”—an investigative technique that helps experts determine authorship by identifying quirks in a writer’s style. Advances in computer technology can now parse text with ever-finer accuracy. Consider the recent outing of Harry Potter author J.K. Rowling as the writer of The Cuckoo’s Calling , a crime novel she published under the pen name Robert Galbraith. England’s Sunday Times , responding to an anonymous tip that Rowling was the book’s real author, hired Duquesne University’s Patrick Juola to analyze the text of Cuckoo , using software that he had spent over a decade refining. One of Juola’s tests examined sequences of adjacent words, while another zoomed in on sequences of characters; a third test tallied the most common words, while a fourth examined the author’s preference for long or short words. Juola wound up with a linguistic fingerprint—hard data on the author’s stylistic quirks. He then ran the same tests on four other books: The Casual Vacancy , Rowling’s first post-Harry Potter novel, plus three stylistically similar crime novels by other female writers. Juola concluded that Rowling was the most likely author of The Cuckoo’s Calling , since she was the only one whose writing style showed up as the closest or second-closest match in each of the tests. After consulting an Oxford linguist and receiving a concurring opinion, the newspaper confronted Rowling, who confessed. Juola completed his analysis in about half an hour. By contrast, in the early 1960s, it had taken a team of two statisticians—using what was then a state-of-the-art, high-speed computer at MIT—three years to complete a project to reveal who wrote 12 unsigned Federalist Papers. Robert Leonard, who heads the forensic linguistics program at Hofstra University, has also made a career out of determining authorship. Certified to serve as an expert witness in 13 states, he has presented evidence in cases such as that of Christopher Coleman, who was arrested in 2009 for murdering his family in Waterloo, Illinois. Leonard testified that Coleman’s writing style matched threats spray-painted at his family’s home (photo, left). Coleman was convicted and is serving a life sentence. Since forensic linguists deal in probabilities, not certainties, it is all the more essential to further refine this field of study, experts say. “There have been cases where it was my impression that the evidence on which people were freed or convicted was iffy in one way or another,” says Edward Finegan, president of the International Association of Forensic Linguists. Vanderbilt law professor Edward Cheng, an expert on the reliability of forensic evidence, says that linguistic analysis is best used when only a handful of people could have written a given text. As forensic linguistics continues to make headlines, criminals may realize the importance of choosing their words carefully. And some worry that software also can be used to obscure distinctive written styles. “Anything that you can identify to analyze,” says Juola, “I can identify and try to hide.

Chapter One Vivek Ranadivé “IT WAS REALLY RANDOM. I MEAN, MY FATHER HAD NEVER PLAYED BASKETBALL BEFORE.” 1. When Vivek Ranadivé decided to coach his daughter Anjali’s basketball team, he settled on two principles. The first was that he would never raise his voice. This was National Junior Basketball—the Little League of basketball. The team was made up mostly of twelve-year-olds, and twelve-year-olds, he knew from experience, did not respond well to shouting. He would conduct business on the basketball court, he decided, the same way he conducted business at his software firm. He would speak calmly and softly, and he would persuade the girls of the wisdom of his approach with appeals to reason and common sense. The second principle was more important. Ranadivé was puzzled by the way Americans play basketball. He is from Mumbai. He grew up with cricket and soccer. He would never forget the first time he saw a basketball game. He thought it was mindless. Team A would score and then immediately retreat to its own end of the court. Team B would pass the ball in from the sidelines and dribble it into Team A’s end, where Team A was patiently waiting. Then the process would reverse itself. A regulation basketball court is ninety-four feet long. Most of the time, a team would defend only about twenty-four feet of that, conceding the other seventy feet. Occasionally teams played a full-court press—that is, they contested their opponent’s attempt to advance the ball up the court. But they did it for only a few minutes at a time. It was as if there were a kind of conspiracy in the basketball world about the way the game ought to be played, Ranadivé thought, and that conspiracy had the effect of widening the gap between good teams and weak teams. Good teams, after all, had players who were tall and could dribble and shoot well; they could crisply execute their carefully prepared plays in their opponent’s end. Why, then, did weak teams play in a way that made it easy for good teams to do the very things that they were so good at? Ranadivé looked at his girls. Morgan and Julia were serious basketball players. But Nicky, Angela, Dani, Holly, Annika, and his own daughter, Anjali, had never played the game before. They weren’t all that tall. They couldn’t shoot. They weren’t particularly adept at dribbling. They were not the sort who played pickup games at the playground every evening. Ranadivé lives in Menlo Park, in the heart of California’s Silicon Valley. His team was made up of, as Ranadivé put it, “little blond girls.” These were the daughters of nerds and computer programmers. They worked on science projects and read long and complicated books and dreamed about growing up to be marine biologists. Ranadivé knew that if they played the conventional way—if they let their opponents dribble the ball up the court without opposition—they would almost certainly lose to the girls for whom basketball was a passion. Ranadivé had come to America as a seventeen-year-old with fifty dollars in his pocket. He was not one to accept losing easily. His second principle, then, was that his team would play a real full-court press—every game, all the time. The team ended up at the national championships. “It was really random,” Anjali Ranadivé said. “I mean, my father had never played basketball before.” 2. Suppose you were to total up all the wars over the past two hundred years that occurred between very large and very small countries. Let’s say that one side has to be at least ten times larger in population and armed might

Let's say I was tasked with determining whether your software project will fail. With the responses to these three questions in hand, I can tell you with almost utter certainty whether your project will fail: How many lines of code will your team write? What kind of software are you building? Do you like your coworkers? That last question isn't a joke. I'm not kidding. Do you like the company of your teammates on a personal level? Do you respect your teammates professionally? If you were starting at another company, would you invite your coworkers along? Do you have spirited team discussions or knock-down, drag-out, last man standing filibuster team arguments? Are there any people on your team you'd "vote off the island" if you could?

Open-source software shows the potential of social norms. In the case of Linux and other collaborative projects, you can post a problem about a bug on one of the bulletin boards and see how fast someone, or often many people, will react to your request and fix the software-using their own leisure time. Could you pay for this level of service? Most likely. But if you had to hire people of the same caliber they would cost you an arm and a leg. Rather, people in these communities are happy to give their time to society at large (for which they get the same social benefits we all get from helping a friend paint a room). What can we learn from this that is applicable to the business world? There are social rewards that strongly motivate behavior-and one of the least used in corporate life is the encouragement of social rewards and reputation.

Corporations began to take a more active and public role in free software projects, contributing time and equipment, and sometimes even directly funding the development of free programs. Such investments could, in the best scenarios, repay themselves many times over. The sponsor only pays a small number of expert programmers to devote themselves to the project full time, but reaps the benefits of everyone’s contributions, including work from unpaid volunteers and from programmers being paid by other corporations.

Identify items that seem likely to change. If the requirements have been done well, they include a list of potential changes and the likelihood of each change. In such a case, identifying the likely changes is easy. If the requirements don't cover potential changes, see the discussion that follows of areas that are likely to change on any project. Separate items that are likely to change. Compartmentalize each volatile component identified in step 1 into its own class or into a class with other volatile components that are likely to change at the same time. Isolate items that seem likely to change. Design the interclass interfaces to be insensitive to the potential changes. Design the interfaces so that changes are limited to the inside of the class and the outside remains unaffected. Any other class using the changed class should be unaware that the change has occurred. The class's interface should protect its secrets. Here are a few areas that are likely to change: Business rules. Business rules tend to be the source of frequent software changes. Congress changes the tax structure, a union renegotiates its contract, or an insurance company changes its rate tables. If you follow the principle of information hiding, logic based on these rules won't be strewn throughout your program. The logic will stay hidden in a single dark corner of the system until it needs to be changed.

Most software disasters start out too small to notice, and most project overruns happen a day at a time.

we want to improve testing to reduce bugs in the system to reduce the duration to deliver new software releases” to financial business cases “with a 80% probability we will achieve benefits between 12.14 and 13.86 million Euro.” (Ritter and Marburger, 2012)

Here are the benefits you can expect from using this style of pseudocode: Pseudocode makes reviews easier. You can review detailed designs without examining source code. Pseudocode makes low-level design reviews easier and reduces the need to review the code itself. Pseudocode supports the idea of iterative refinement. You start with a high-level design, refine the design to pseudocode, and then refine the pseudocode to source code. This successive refinement in small steps allows you to check your design as you drive it to lower levels of detail. The result is that you catch high-level errors at the highest level, mid-level errors at the middle level, and low-level errors at the lowest level—before any of them becomes a problem or contaminates work at more detailed levels. Pseudocode makes changes easier. A few lines of pseudocode are easier to change than a page of code. Would you rather change a line on a blueprint or rip out a wall and nail in the two-by-fours somewhere else? The effects aren't as physically dramatic in software, but the principle of changing the product when it's most malleable is the same. One of the keys to the success of a project is to catch errors at the "least-value stage," the stage at which the least effort has been invested. Much less has been invested at the pseudocode stage than after full coding, testing, and debugging, so it makes economic sense to catch the errors early.

NASA's Software Engineering Laboratory studied ten projects that pursued reuse aggressively (McGarry, Waligora, and McDermott 1989). In both the object-oriented and the functionally oriented approaches, the initial projects weren't able to take much of their code from previous projects because previous projects hadn't established a sufficient code base. Subsequently, the projects that used functional design were able to take about 35 percent of their code from previous projects. Projects that used an object-oriented approach were able to take more than 70 percent of their code from previous projects. If you can avoid writing 70 percent of your code by planning ahead, do it!

Separate organizations with related software needs often find themselves duplicating effort, either by redundantly writing similar code in-house, or by purchasing similar products from proprietary vendors. When they realize what’s going on, the organizations may pool their resources and create (or join) an open source project tailored to their needs. The advantages are obvious: the costs of development are divided, but the benefits accrue to all.

Most literature on the subject of agile methodology... is written from the viewpoint of software developers and programmers, and tends to place its main emphasis on programming techniques and agile project management—testing is usually only mentioned in the guise of unit testing and its associated tools. ...However, unit tests alone are not sufficient and broader-based testing is critical to the success of agile development processes.

Recommended Reading Mike Cohn Agile Estimating and Planning provides guidance on iteration planning, including estimating the effort for user stories. David J. Anderson Kanban: Successful Evolutionary Change for Your Technology Business provides the guidance, definitions, and metric calculations necessary to establish an efficient software development flow, including establishing WIP limits.

Vel Technologies,is a Software Development and Web Designing Company. It started its services in 2009.Vel Technologies have 2 branches in Madurai, Tamilnadu.

Cassandra is now 5 years old. It is an active open source project in the Apache Software Foundation and therefore it is known as Apache Cassandra as well. Cassandra can manage huge volume of structured, semi-structured, and unstructured data in a large distributed cluster across multiple data centers. It provides linear scalability, high performance, fault tolerance, and supports a very flexible data model.