Software Developer Quotes

Walking on water and developing software from a specification are easy if both are frozen.

Software development, like professional sports, has a way of making thirty-year-old men feel decrepit.

Always be the worst guy in every band you’re in. - so you can learn. The people around you affect your performance. Choose your crowd wisely.

We build our computers the way we build our cities—over time, without a plan, on top of ruins.

The ideal architect should be a man of letters, a skillful draftsman, a mathematician, familiar with historical studies, a diligent student of philosophy, acquainted with music, not ignorant of medicine, learned in the responses of jurisconsults, familiar with astronomy and astronomical calculations.

We have four blocks here. Block A, where we are now, is administration and recreation. Block B is software development. Block C is research and storage. Block D is where the main Stormbreaker assembly line is found.” “Where’s breakfast?” Alex asked.

With software there are only two possibilites: either the users control the programme or the programme controls the users. If the programme controls the users, and the developer controls the programme, then the programme is an instrument of unjust power.

A society where feminine beauty is defined not by the human self on genuine intellectual and sentimental grounds, but by a computer software on the grounds of economic interest, is more dead than alive. It is a society of human bodies, not human beings.

Every good work of software starts by scratching a developer’s personal itch.

Software testing is a sport like hunting, it's bughunting.

Programming is breaking of one big impossible task into several very small possible tasks.

In a small company, the CTO, R&D, the COO, and even the CEO or cofounders or owners can be responsible for reviewing documentation. Don’t rely on your memory; write it down. Ideas become reality when we speak them and write them. So document them in an idea journal (digital or traditional) without judgment at the time. Inventors (and especially software developers) tend to edit or judge ideas and conclude they are not patentable because they were simple—even though they solve important problems and do not exist elsewhere.

DEDICATION To my computer: I couldn’t have written this without you To the software developers responsible for spellcheck: You are my everyday heroes To Karen: I hope this makes you laugh and makes you proud. To my readers (all 3 of you): Thank you

If it is not written down, it does not exist.

Being the only woman on a nontechnical team, providing customer support to software developers, was like immersion therapy for internalized misogyny. I liked men—I had a brother. I had a boyfriend. But men were everywhere: the customers, my teammates, my boss, his boss. I was always fixing things for them, tiptoeing around their vanities, cheering them up. Affirming, dodging, confiding, collaborating. Advocating for their career advancement; ordering them pizza. My job had placed me, a self-identified feminist, in a position of ceaseless, professionalized deference to the male ego.

Advancement only comes with habitually doing more than you are asked.” —Gary Ryan Blair

Programming is a social activity.

The biggest cause of failure in software-intensive systems is not technical failure; it’s building the wrong thing.

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.

The moment I walk into a bookstore, I remember what I love about them. They are an oasis of intellectual calm. Perhaps it’s the potential of all the ideas hidden behind those delicious covers. Or perhaps it’s the social reverence for the library-like quiet. You don’t yell in a bookstore; you’ll piss off the books.

Einstein repeatedly argued that there must be simplified explanations of nature, because God is not capricious or arbitrary. No such faith comforts the software engineer.

Almost everything we know about good software architecture has to do with making software easy to change

Your job as a developer is not just to create code that you can work with easily, but to create code that others can also work with easily.

As a software developer, you are your own worst enemy. The sooner you realize that, the better off you’ll be.

We see a lot of feature-driven product design in which the cost of features is not properly accounted. Features can have a negative value to customers because they make the products more difficult to understand and use. We are finding that people like products that just work. It turns out that designs that just work are much harder to produce that designs that assemble long lists of features.

Albert Ellis: “The best predictor of future behaviour is past behaviour”. Apart

We had hundreds of health-care workers from across the world flying in to take action, and software developers constantly coming up with new, pointless Ebola apps (apps were their hammers and they were desperate for Ebola to be a nail). But no one was tracking whether the action was working or not.

User interface is the process of shifting from chaotic complexity to elegant simplicity.

In the end, it all comes down to 0 and 1

Life would be much easier if I had the source code.

Software development is neither a scientific nor an engineering task. It is an act of reality construction that is political and artistic.

How many software developers does it take to change a lightbulb? None, it's a hardware problem.

I know that this sounds sacrilegious to a software developer, but unless you’re marketing to software developers, your order of importance is market, marketing, aesthetic, function.

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.

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

Almost every software development organization has at least one developer who takes tactical programming to the extreme: a tactical tornado. The tactical tornado is a prolific programmer who pumps out code far faster than others but works in a totally tactical fashion. When it comes to implementing a quick feature, nobody gets it done faster than the tactical tornado. In some organizations, management treats tactical tornadoes as heroes. However, tactical tornadoes leave behind a wake of destruction. They are rarely considered heroes by the engineers who must work with their code in the future. Typically, other engineers must clean up the messes left behind by the tactical tornado, which makes it appear that those engineers (who are the real heroes) are making slower progress than the tactical tornado.

Perhaps you thought that “getting it working” was the first order of business for a professional developer. I hope by now, however, that this book has disabused you of that idea. The functionality that you create today has a good chance of changing in the next release, but the readability of your code will have a profound effect on all the changes that will ever be made.

In software development, “perfect” is a verb, not an adjective. There is no perfect process. There is no perfect design. There are no perfect stories. You can, however, perfect your process, your design, and your stories.

Software craftsmanship is a long journey to mastery. It’s a mindset where software developers choose to be responsible for their own careers, constantly learning new tools and techniques and constantly bettering themselves.

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.

So many people set off in a direction in life but don’t think things completely through first.

When I'm old and dying, I plan to look back on my life and say, "Wow, that was an adventure", not, "Wow, I sure felt safe." - Tom Preston-Werner

Software will give you respect, but hardware will give you the Power.

Launch is just another point in software’s life. Not the end-all and be-all.

In June 1999, an 18-year-old Northeastern University dropout by the name of Shawn Fanning debuted a new piece of software he had developed called Napster.

Computers themselves, and software yet to be developed, will revolutionize the way we learn.

You can Change Your Organization or Change Your Organization

Quality must be enforced, otherwise it won't happen. We programmers must be required to write tests, otherwise we won't do it.

You can’t creatively help a business until you know how it works.

customers do not need scope. They need to have business goals accomplished within some constraints of time and cost.

Coding like poetry should be short and concise.

Trying to improve software quality by increasing the amount of testing is like trying to lose weight by weighing yourself more often. What you eat before you step onto the scale determines how much you will weigh, and the software-development techniques you use determine how many errors testing will find.

Senior engineers can develop bad habits, and one of the worst is the tendency to lecture and debate with anyone who does not understand them or who disagrees with what they are saying. To work successfully with a newcomer or a more junior teammate, you must be able to listen and communicate in a way that person can understand, even if you have to try several times to get it right. Software development is a team sport in most companies, and teams have to communicate effectively to get anything done.

Have you ever had a weird and strong feeling that programming is a godlike kind of work? Just as the Lord created our world and the entire Universe based on molecular techniques such as DNA coding, software developers create a digital world based on IT coding.

We used the word “heuristics” to describe aspects of software development that tip toward the liberal arts. Its counterpart, “algorithms,” was its alter ego on the technical side. Heuristics and algorithms are like two sides of the same coin. Both are specific procedures for making software do what it does: taking input, applying an operation, and producing output. Yet each had a different purpose.

I briefly dated a software developer. We went to this wonderful restaurant a couple of times and had this delicious chicken with these diverse, tangy sauces—artichoke garlic aioli, Thai sweet chili—and we talked about whatever while I ate this chicken and dipped the pieces into the otherworldly sauces. Meanwhile I thought, God, I think I really like him. Then we went back again and had the same chicken and sauces—and I thought, God, I feel like I’m really falling for him. Then we went on a third date to a different restaurant and I suddenly realized—now that the chicken and sauces had been removed—he was kind of boring and it was just the tasty chicken that I loved. I looooooooooove chicken.

I’d prefer not to say what my current salary is because if it’s higher than what you expect to pay for this job, I wouldn’t want that to eliminate me from being considered for this job—because I might be willing to accept less for the right position—and, if it’s lower than what this job would pay, I wouldn’t want to sell myself short either— I’m sure you can understand.

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.

Every time you say blah blah blah, a creative writing teacher dies.

Developers should be able to run all automated tests on their workstations in order to triage and fix defects.

Just as the Hare was overconfident in its speed, so the developers are overconfident in their ability to remain productive.

It’s better to have a hole in your team than an asshole in your team!

Suppose a developer has a conversation with a customer about details of a feature. The conversation should not be considered complete until it is expressed as a customer test.

Celebrate Successes, but Don't Declare Victory

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

Software lives and matures over time.

Humility is not just something we develop so we can claim to be more spiritual. It also allows you to see your actions more clearly.

Your skills should transcend technology platform

Concepts and patterns that your brain is sorting through and making sense of are much more scalable and universal than any specific vendor’s technology

If you want to stay relevant, you’re going to have to dive into the domain of the business you’re in

The easiest way to never get anything done is to never commit to anything.

The higher the price of information in a software team, the less effective the team is.

We, newbies and young programmers, don't like chaos because it makes us dependent on experts. We have to beg for information and feel bad

Automated testing is a safety net that protects the program from its programmers

Education requires both a teacher and a student. Many of us are too often reluctant to be a student.

If you want to really learn something, try teaching it to someone else.

With credibility comes influence.

Walking on water and developing software to specification are easy as long as both are frozen.

This is what makes them good engineers. Perfectionism: incinerating perfectionism.

We must not blame programmers for their bugs. They belong to them only until the code is merged to the repository. After that, all bugs are ours!

IF YOU DON’T FEED YOUR MIND WITH SUCCESS. IT WILL ROT WITH MEDIOCRITY!

Software Development is an ideal gas: it occupies all the volume it can.

I became a sponge. A new chapter began in my own education, and I dual majored in corporate politics and software development in the real world.

Testing was never going to be fashionable, but you could hardly run a respectable software development shop with no testing effort at all.

Software developers, mathematicians, and game-theory modelers aren’t running away with all the rewards; it is the people who have the most common sense, imagination, and determination.

Softwares are becoming the new cargo ships and freight trucks. Digital files are becoming the new core commodities. The formers won't eliminate the latters, but a restructuring is happening.

Is a mind a complicated kind of abstract pattern that develops in an underlying physical substrate, such as a vast network of nerve cells? If so, could something else be substituted for the nerve cells – something such as ants, giving rise to an ant colony that thinks as a whole and has an identity – that is to say, a self? Or could something else be substituted for the tiny nerve cells, such as millions of small computational units made of arrays of transistors, giving rise to an artificial neural network with a conscious mind? Or could software simulating such richly interconnected computational units be substituted, giving rise to a conventional computer (necessarily a far faster and more capacious one than we have ever seen) endowed with a mind and a soul and free will?

There should be two tasks for a human being to perform to deploy software into a development, test, or production environment: to pick the version and environment and to press the “deploy” button.

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.

Hollywood and similar “popular culture” sources of disinformation have assigned largely negative images to programmers. For example, we have all seen the solitary, fat, ugly nerd with no social skills who is obsessed with video games and breaking into other people’s computers. He (almost always a male) is as likely to want to destroy the world as he is to want to save it. Obviously, milder versions of such caricatures exist in real life, but in our experience they are no more frequent among software developers than they are among lawyers, police officers, car salesmen, journalists, artists, or politicians.

If software developers should always be thinking about design issues, and reducing complexity is the most important element of software design, then software developers should always be thinking about complexity.

Thankfully for frustrated women around the world, Tom Schalk, the vice president of voice technology at car navigation system supplier ATX, has come up with a novel solution to fix the ‘many issues with women’s voices’.26 What women need, he said, was ‘lengthy training’ – if only women ‘were willing’ to submit to it. Which, sighs Schalk, they just aren’t. Just like the wilful women buying the wrong stoves in Bangladesh, women buying cars are unreasonably expecting voice-recognition software developers to design a product that works for them when it’s obvious that the problem needing fixing is the women themselves. Why can’t a woman be more like a man?

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.

As the population of software developers ages, they care more about the rest of their lives. Many lament wasting their twenties locked up in an office slaving over a piece of code that failed to reach market expectations and became obsolete soon after release. Work/life

Software development is the process of creating a computer software. It includes preparing a design, coding the program, and fixing the bugs. The final goal of software development is to translate user needs to software product, while continuously improving the team and the process.

What would the world be like if you had to develop a power yourself before you could use it? Just as a silly example: How would the comment section on YouTube change if, to use it, you had to have the schooling necessary to have a basic understanding of how computers and the internet work? More seriously, would anyone smart enough to know how to design and build a tank, or a laser guided anti-aircraft missile, or a computer and video editing software be stupid enough to join ISIS? In fact, if such knowledge was required—would it even be possible for there to be standing armies?

When you yet to do 100% of what somebody wants, you need a perfect match, and it's pretty rare that you have a perfect match between what you thought people needed and what they actually need. If you try instead to do 80 percent of what they need, there's a pretty good chance you'll hit a sweet spot.

The Joel Test 1. Do you use source control? 2. Can you make a build in one step? 3. Do you make daily builds? 4. Do you have a bug database? 5. Do you fix bugs before writing new code? 6. Do you have an up-to-date schedule? 7. Do you have a spec? 8. Do programmers have quiet working conditions? 9. Do you use the best tools money can buy? 10. Do you have testers? 11. Do new candidates write code during their interview? 12. Do you do hallway usability testing?

It is a myth that we can get systems “right the first time.” Instead, we should implement only today’s stories, then refactor and expand the system to implement new stories tomorrow. This is the essence of iterative and incremental agility. Test-driven development, refactoring, and the clean code they produce make this work at the code level.

A good program must be written many times. This is true of the programs we show. The first draft may not clearly separate out the concerns, but by making that draft the programmer learns the structure of the problem. We will show two different implementations, which will reveal the evolution of the program as we identify shortcomings in our draft.

Today I am more convinced than ever. Conceptual integrity is central to product quality. Having a system architect is the most important single step toward conceptual integrity. These principles are by no means limited to software systems, but to the design of any complex construct, whether a computer, an airplane, a Strategic Defense Initiative, a Global Positioning System. After teaching a software engineering laboratory more than 20 times, I came to insist that student teams as small as four people choose a manager and a separate architect. Defining distinct roles in such small teams may be a little extreme, but I have observed it to work well and to contribute to design success even for small teams.

What we learned is that when you conduct experiments, you should remember to hold back resources to give needed rocket boosters to the winning experiments.

In general, the longer you wait before fixing a bug, the costlier (in time and money) it is to fix.

People in any field rise to the expectations set for them.

You Do Not Delegate Accountability

If you see me make sure you say I Don't Do It, U Do It!!!

Code formatting is about communication, and communication is the professional developer’s first order of business.

Complexity kills. It sucks the life out of developers, it makes products difficult to plan, build, and test.” —Ray Ozzie, CTO, Microsoft Corporation

You do not win a race by trying not to loose

Always be the worst guy in every band you are in.

The job of the channel(s) is to find, win, make, keep and grow happy customers. In

Many software executives consider the independent channel partners as a readily available, flexible and inexpensive sales resource and nothing could be further from the truth. I

Software quality begins with the quality of the requirements.

Software always remain softly for End users! But sometimes hardly to developers!

about 48 percent of GE’s software is developed in India.

It may seem like writing tests slows down development; in fact, testing does not cost, it pays, both during development and over the system’s lifecycle.

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

Portability is for canoes.

To focus on the visible at the expense of the essential is irresponsible.

Stay flexible, remember what it means to be an engineer, and don’t stop developing.

Lean does not mean letting the inmates run the asylum.

thing that kills an entrepreneurial, experimental culture is when people get punished for running an experiment that proves a hypothesis false. (Note that I don’t call this “failing.”)

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.

In November, just over four months after shipping its first iPhone, Apple revealed that it would make available a software development kit for anyone who wanted to develop apps. “That’s when we knew Steve had finally come to see the light,” Gassée says. “Suddenly, that was all anyone was talking about in the Valley and in the VC community. Hundreds of little guys signed up, and the race was on. Then they announced the App Store. And then they released the iPhone 3G [the second version, which shipped in July 2008, and had better wireless and a faster microprocessor]. It was only then that the iPhone was truly finished, that it had all its basics, all its organs. It needed to grow, to muscle up, but it was complete as a child is complete.

To communicate effectively, the code must be based on the same language used to write the requirements—the same language that the developers speak with each other and with domain experts.

Richard Charnin is an author and quantitative software developer with advanced degrees in applied mathematics and operations research. He paints a very clear portrait of the JFK witness deaths in the context of the mathematical landscape: I have proved mathematically what many have long suspected: The scores of convenient JFK unnatural witness deaths cannot be coincidental.15

...I’m not saying simple code takes less time to write. You’d think it would since you end up with less total code, but a good solution isn’t an accretion of code, it’s a distillation of it.

The Principle of Least Surprise" describes a general approach to software that celebrates sanity over cleverness: clear intent, reasonable defaults, and providing a sense of control to the developer.

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%).

People who are effective at developing high-quality software have spent years accumulating dozens of techniques, tricks, and magic incantations. The techniques are not rules; they are analytical tools.

he bragged that he’d written a million lines of code. Some employees thought that was preposterous. Sunny had worked at Microsoft, where teams of software engineers had written the Windows operating system at the rate of one thousand lines of code per year of development. Even if you assumed Sunny was twenty times faster than the Windows developers, it would still have taken him fifty years to do what he claimed.

Being a leader doesn’t mean you have people reporting to you on an organizational chart—leadership is about inspiring and motivating those around you. A good leader affects a team’s ability to deliver code, architect good systems, and apply Lean principles to how the team manages its work and develops products. All of these have a measurable impact on an organization’s profitability, productivity, and market share.

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!

Code formatting is important. It is too important to ignore and it is too important to treat religiously. Code formatting is about communication, and communication is the professional developer’s first order of business.

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

Ethereum is the second-biggest cryptocurrency in the world after Bitcoin. It’s also very different from Bitcoin in its structure and purpose. Ethereum wasn’t developed as a currency alone. Its innovation lies in opening the blockchain up to development for different applications outside currencies and finance. Developers can build software on top of Ethereum’s blockchain, and use the network’s distributed ledger to build trust for all kinds of applications. Since the Ethereum blockchain is decentralized, once a developer has built an application, it can’t be censored or taken down by any authority. That application lives as long as the Ethereum blockchain continues.

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.

Budgets and plans have three purposes: (1) Set goals, (2) make forecasts, and (3) allocate resources. It would seem efficient to use a single plan to accomplish all three purposes, but in fact, combining the purposes compromises all of them.

Clean code can be read, and enhanced by a developer other than its original author. It has unit and acceptance tests. It has meaningful names. It provides one way rather than many ways for doing one thing. It has minimal dependencies, which are explicitly defined, and provides a clear and minimal API. Code should be literate since depending on the language, not all necessary information can be expressed clearly in code alone. -Dave Thomas, founder of OTI, godfather of the Eclipse strategy

Software developers come mainly from engineering and don’t see how similar their industry has become to the one that produces magazines, newspapers, books, TV shows, and movies. Most software developers haven’t yet learned to develop and follow strict standards for layout and graphic design and to pay as much attention to detail as traditional publishers and media studios do. As a result, graphic design and layout bloopers often get a “Who cares? It looks OK to me!” reaction from developers.

You could have chosen any number of career paths, but this one is exciting. It’s creative. It requires deep thinking and rewards you with a sense of being able to do something that most of the people you meet each day can’t imagine being able to do. We may worry about progressing to the next level, making an impact, or gaining respect from our co-workers or our peers in the industry, but if you really stop to think about it, we’ve got it really good. Software development is both challenging and rewarding. It’s creative like an art-form, but (unlike art) it provides concrete,measurable value. Software development is fun! Ultimately, the most important thing I’ve learned over the journey that my career in software development has been is that it’s not what you do for a living or what you have that’s important. It’s how you choose to accept these things. It’s internal. Satisfaction, like our career choices, is something that should be sought after and decided upon with intention.

In the modern computer, software has developed in such a way as to fill this role of go-between. On one end you have the so-called end user who wants to be able to order up a piece of long division, say, simply by supplying two numbers to the machine and ordering it to divide them. At the other end stands the actual computer, which for all its complexity is something of a brute. It can perform only several hundred basic operations, and long division may not be one of them. The machine may have to be instructed to perform a sequence of several of its basic operations in order to accomplish a piece of long division. Software—a series of what are known as programs—translates the end user’s wish into specific, functional commands for the machine.

The job of tests, and the people that develop and runs tests, is to prevent defects, not to find them. A quality assurance organization should champion processes that build quality into the code from the start rather than test quality in later. This is not to say that verification is unnecessary. Final verification is a good idea. It’s just that finding defects should be the exception, not the rule, during verification. If verification routinely triggers test-and-fix cycles, then the development process is defective.

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.

Microsoft has a division that studies the way people work, to develop efficiency-improving software. (According to Microsoft’s research up to 2007, if you’re looking for a technological solution to being more efficient, getting a bigger computer screen is one of the few clear winners.)

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.

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.

Children develop self-confidence when they learn simple skills like pulling up a zipper, tying their shoes, or riding a bike. Eventually, that self-confidence evolves and propels them to develop more complex abilities as adults—for instance, writing software, painting murals, or cheering up a disheartened friend.

instead of letting developers just run around and do whatever they want, autonomy actually has its basis in rules. Without guardrails, people won’t know how to make decisions, and leaders will tend to second-guess them constantly. By creating rules, you paradoxically set people free—in the space between guardrails.

as we provide our software solutions in a service based format we get something in return that the on-premise didn’t provide: insight. We can actually see how users are using our services and where they have issues and challenges and with this insight we can do something about improving the value and minimizing the churn.

A generation ago, fun wasn’t a deciding factor when we talked about career choices. Jobs aren’t supposed to be fun. They’re supposed to bring home the bacon. Fun is what you do on your off days. Fun happens in the evenings and weekends. But if your job isn’t fun, as we’ve come to realize, you don’t do a fantastic job at it.

Years later, when I got to college, I learned about an important theory of psychology called Learned Helplessness, developed by Dr. Martin E. P. Seligman. This theory, backed up by years of research, is that a great deal of depression grows out of a feeling of helplessness: the feeling that you cannot control your environment.

Countering the juggernaut of formalism is a minority worldview of equal historical standing, even though it does not share equal awareness or popularity. Variously known as hermeneutics, constructivism, interpretationalism, and most recently postmodernism, this tradition has consistently challenged almost everything advanced by the formalists. Iterative development practices, including XP, and object thinking are consistent with the hermeneutic worldview. Unfortunately, most object, XP, and agile practitioners are unaware of this tradition and its potential for providing philosophical support and justification for their approach to software development.

Developing software that delivers true business value is not the same thing as developing ordinary business software. Software that delivers true business value aligns with the business strategic initiatives and bears solutions with clearly identifiable competitive advantage—software that is not about technology, but about the business.

In Webvan’s case premature scaling was an integral part of the company culture and the prevailing venture capital “get big fast” mantra. Webvan spent $18 million to develop proprietary software and $40 million to set up its first automated warehouse before it had shipped a single item. Premature scaling had dire consequences since Webvan’s spending was on a scale that ensures it will be taught in business school case studies for years to come. As customer behavior continued to differ from the predictions in Webvan’s business plan, the company slowly realized it had overbuilt and over-designed. The business model made sense only at the high volumes predicted on the spreadsheet.

To be a software developer was to run the rest stops off the exits and to make sure that all the fast-food and gas station franchises accorded with each other and with user expectations; to be a hardware specialist was to lay the infrastructure, to grade and pave the roads themselves; while to be a network specialist was to be responsible for traffic control, manipulating signs and lights to safely route the time-crunched hordes to their proper destinations. To get into systems, however, was to be an urban planner, to take all of the components available and ensure their interaction to maximum effect. It was, pure and simple, like getting paid to play God, or at least a tinpot dictator.

Still allergic to PowerPoints and formal presentations, he insisted that the people around the table hash out issues from various vantages and the perspectives of different departments. Because he believed that Apple's great advantage was its integration of the whole widget- from design to hardware to software to content-he wanted all departments at the company to work together in parallel. The phrases he used were "deep collaboration" and "concurrent engineering." Instead of a development process in which a product would be passed sequentially from engineering to design to manufacturing to marketing and distribution, these various departments collaborated simultaneously. " Our method was to develop integrated products, and that meant our process had to be integrated and collaborative," Jobs said. This approach also applied to key hires. He would have candidates meet the top leaders-Cook, Tevanian, Schiller, Rubinstein, Ive- rather than just the managers of the department where they wanted to work. " Then we all get together without the person and talk about whether they'll fit in," Jobs said.

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.

Genisys, a Google Adwords-certified leading Digital Marketing Agency is operating multi facet digital services throughout India specializing in Web development, Web design, Software development, Digital marketing services which include-SEO (Search Engine Optimization), SMM (Social Media Marketing), PPC(Pay Per Click), Email marketing, Content marketing, Mobile marketing, Affiliate marketing, Brand marketing and promotion, inbound marketing, Local Business Marketing, Business listing solution, Video brochure, Ecommerce solution, CRM service, Reputation Management, Online Presence analysis, Conversion Rate Optimization, Goggle service and so on to keep up with the high-tech advanced digital world and connecting the clients goal to reality through creative designers, digital strategists and specialized innovative team.

Is a mind a complicated kind of abstract pattern that develops in an underlying physical substrate, such as a vast network of nerve cells? If so, could something else be substituted for the nerve cells – something such as ants, giving rise to an ant colony that thinks as a whole and has an identity – that is to say, a self? Or could something else be substituted for the tiny nerve cells, such as millions of small computational units made of arrays of transistors, giving rise to an artificial neural network with a conscious mind? Or could software simulating such richly interconnected computational units be substituted, giving rise to a conventional computer (necessarily a far faster and more capacious one than we have ever seen) endowed with a mind and a soul and free will? In short, can thinking and feeling emerge from patterns

The label “jack-of-all-trades but master of none” is normally meant to be derogatory, implying that the labelee lacks the focus to really dive into a subject and master it. But, when your online shopping application is on the fritz and you’re losing orders by the hundreds as each hour passes, it’s the jack-of-all-trades who not only knows how the application’s code works but can also do low-level UNIX debugging of your web server processes, analyze your RDBMS’s configuration for potential performance bottlenecks, and check your network’s router configuration for hard-to-find problems. And, more important, after finding the problem, the jack-of-all-trades can quickly make architecture and design decisions, implement code fixes, and deploy a new fixed system to production. In this scenario, the manufacturing scenario seems quaint at best and critically flawed at worst.

Program maintenance involves no cleaning, lubrication, or repair of deterioration. It consists chiefly of changes that repair design defects. Much more often than with hardware, these changes include added functions. Usually they are visible to the user. The total cost of maintaining a widely used program is typically 40 percent or more of the cost of developing it. Surprisingly, this cost is strongly affected by the number of users. More users find more bugs.

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!

Bitcoin’s Test Blockchains You might be surprised to learn that there is more than one bitcoin blockchain. The “main” bitcoin blockchain, the one created by Satoshi Nakamoto on January 3rd, 2009, the one with the genesis block we studied in this chapter, is called mainnet. There are other bitcoin blockchains that are used for testing purposes: at this time testnet, segnet, and regtest. Let’s look at each in turn. Testnet — Bitcoin’s Testing Playground Testnet is the name of the test blockchain, network, and currency that is used for testing purposes. The testnet is a fully featured live P2P network, with wallets, test bitcoins (testnet coins), mining, and all the other features of mainnet. There are really only two differences: testnet coins are meant to be worthless and mining difficulty should be low enough that anyone can mine testnet coins relatively easily (keeping them worthless). Any software development that is intended for production use on bitcoin’s mainnet should first be tested on testnet with test coins. This protects both the developers from monetary losses due to bugs and the network from unintended behavior due to bugs.

The ethical implications of these phenomena are significant on individual, local, and global scales. Our desires and consumption habits reflect the physical and emotional health of our persons and our societies. They shape the activities that bind our family and community lives; the kinds and amounts of natural resources that are extracted, used, priced, and distributed; and the type and amount of environmental waste that is produced by those activities. Not only material goods but increasingly, virtual goods, relationships, and experiences fill the ever-expanding catalog of things we are invited to desire and pursue. Online app and game developers encourage us to spend collective billions of human hours growing virtual crops in Farmville, massacring pigs with Angry Birds, or solving new puzzles in the Candy Kingdom. Advanced techniques of software design psychology magnify the addictive (the preferred software nomenclature is ‘sticky’) qualities of apps, driving users to make more and more in-app purchases, share our monetizable information or contacts, or just keep playing into the wee hours of the night to reach whatever surprises await us on the next game level.

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.

Some societies and religions have a tendency to expand the moral circle and to consider all humans as belonging to a single moral community. Hence the Universal Declaration of Human Rights," and hence calls for development aid. Indeed, animals can be drawn into the moral circle: people form associations or even political parties to protect animal rights, and pet animals are solemnly buried. However, in such a vast moral circle, rights and duties are necessarily diluted. Historically, religions that were tolerant of religious diversity have lost out against those that were more closed on themselves. Most empires have disintegrated from the inside.

Take Evernote, a start-up that offers productivity and organization software, which made the companywide decision to delay spending even a penny on marketing for the first several years of its growth. As Evernote’s founder, Phil Libin, told a group of entrepreneurs in a now-classic talk, “People [who are] thinking about things other than making the best product, never make the best product.” So Evernote took “marketing” off the table and instead poured that budget into product development. This undoubtedly slowed brand building at first—but it paid off. Why? Because Evernote is far and away the most superior productivity and note-taking application on the planet. Today, it practically markets itself.

As black-box technologies become more widespread, there have been no shortage of demands for increased transparency. In 2016 the European Union's General Data Protection Regulation included in its stipulations the "right to an explanation," declaring that citizens have a right to know the reason behind the automated decisions that involve them. While no similar measure exists in the United States, the tech industry has become more amenable to paying lip service to "transparency" and "explainability," if only to build consumer trust. Some companies claim they have developed methods that work in reverse to suss out data points that may have triggered the machine's decisions—though these explanations are at best intelligent guesses. (Sam Ritchie, a former software engineer at Stripe, prefers the term "narratives," since the explanations are not a step-by-step breakdown of the algorithm's decision-making process but a hypothesis about reasoning tactics it may have used.) In some cases the explanations come from an entirely different system trained to generate responses that are meant to account convincingly, in semantic terms, for decisions the original machine made, when in truth the two systems are entirely autonomous and unrelated. These misleading explanations end up merely contributing another layer of opacity. "The problem is now exacerbated," writes the critic Kathrin Passig, "because even the existence of a lack of explanation is concealed.

Nevertheless, by dint of his personality and controlling instincts, Jobs was soon playing a stronger role. He spewed out a stream of ideas - some reasonable, others wacky - about what Pixar's hardware and software could become. And on his occasional visits to the PIxar offices, he was an inspiring presence. "I grew up a Southern Baptist, and we had revival meetings with mesmerizing but corrupt preachers," recounted Alvy Ray Smith. "Steve's got it: the power of the tongue and the web of words that catches people up. We were aware of this when we had board meetings, so we developed signals - nose scratching or ear tugs - for when someone had been caught up in Steve's distortion field and he needed to be tugged back to reality.

It is best to be the CEO; it is satisfactory to be an early employee, maybe the fifth or sixth or perhaps the tenth. Alternately, one may become an engineer devising precious algorithms in the cloisters of Google and its like. Otherwise, one becomes a mere employee. A coder of websites at Facebook is no one in particular. A manager at Microsoft is no one. A person (think woman) working in customer relations is a particular type of no one, banished to the bottom, as always, for having spoken directly to a non-technical human being. All these and others are ways for strivers to fall by the wayside — as the startup culture sees it — while their betters race ahead of them. Those left behind may see themselves as ordinary, even failures.

By tracing the early history of USCYBERCOM it is possible to understand some of the reasons why the military has focused almost completely on network defense and cyber attack while being unaware of the need to address the vulnerabilities in systems that could be exploited in future conflicts against technologically capable adversaries. It is a problem mirrored in most organizations. The network security staff are separate from the endpoint security staff who manage desktops through patch and vulnerability management tools and ensure that software and anti-virus signatures are up to date. Meanwhile, the development teams that create new applications, web services, and digital business ventures, work completely on their own with little concern for security. The analogous behavior observed in the military is the creation of new weapons systems, ISR platforms, precision targeting, and C2 capabilities without ensuring that they are resistant to the types of attacks that USCYBERCOM and the NSA have been researching and deploying. USCYBERCOM had its genesis in NCW thinking. First the military worked to participate in the information revolution by joining their networks together. Then it recognized the need for protecting those networks, now deemed cyberspace. The concept that a strong defense requires a strong offense, carried over from missile defense and Cold War strategies, led to a focus on network attack and less emphasis on improving resiliency of computing platforms and weapons systems.

Improve performance through process improvements introduced with minimal resistance. Deliver with high quality. Deliver a predictable lead time by controlling the quantity of work-in-progress. Give team members a better life through an improved work/life balance. Provide slack in the system by balancing demand against throughput. Provide a simple prioritization mechanism that delays commitment and keeps options open. Provide a transparent scheme for seeing improvement opportunities, thereby enabling change to a more collaborative culture that encourages continuous improvement. Strive for a process that enables predictable results, business agility, good governance, and the development of what the Software Engineering Institute calls a high-maturity organization.

You can see Musk’s embrace of the car as lifestyle in Tesla’s abandonment of model years. Tesla does not designate cars as being 2014s or 2015s, and it also doesn’t have “all the 2014s in stock must go, go, go and make room for the new cars” sales. It produces the best Model S it can at the time, and that’s what the customer receives. This means that Tesla does not develop and hold on to a bunch of new features over the course of the year and then unleash them in a new model all at once. It adds features one by one to the manufacturing line when they’re ready. Some customers may be frustrated to miss out on a feature here and there. Tesla, however, manages to deliver most of the upgrades as software updates that everyone gets, providing current Model S owners with pleasant surprises.

Scalable Social Network Analysis. The SSNA would monitor telephone calls, conference calls, and ATM withdrawals, but it also sought to develop a far more invasive surveillance technology, one that could “capture human activities in surveillance environments.” The Activity Recognition and Monitoring program, or ARM, was modeled after England’s CCTV camera. Surveillance cameras would be set up across the nation, and through the ARM program, they would capture images of people as they went about their daily lives, then save these images to massive data storage banks for computers to examine. Using state-of-the-art facial recognition software, ARM would seek to identify who was behaving outside the computer’s pre-programmed threshold for “ordinary.” The parameters for “ordinary” remain classified.

Entrepreneurship itself is an emergent system, where companies create the conditions for experimentation and learning to occur, often symbiotically with customers. In 1978, Eric von Hippel (my PhD advisor at MIT) pioneered the notion of user-driven innovation.10, 11 Back then, the conventional wisdom was that innovation only came from corporate, government, and university research-and-development labs. While some still believe this today, Eric's insight proved to be prescient in many areas, especially in the information age, as the widespread adoption of open-source software and Lean Startup methodologies have demonstrated.12 Twitter is a tangible example since three of the platform's most popular features—the @ reply, the # hashtag indexing, and retweet sharing—were all generated bottom-up by users.

One approach involves looking at three different kinds of bias: physical bias, computational bias, and interpretation bias. This approach was proposed by UCLA engineering professor Achuta Kadambi in a 2021 Science paper.26 Physical bias manifests in the mechanics of the device, as when a pulse oximeter works better on light skin than darker skin. Computational bias might come from the software or the dataset used to develop a diagnostic, as when only light skin is used to train a skin cancer detection algorithm. Interpretation bias might occur when a doctor applies unequal, race-based standards to the output of a test or device, as when doctors give a different GFR threshold to Black patients. “Bias is multidimensional,” Kadambi told Scientific American. “By understanding where it originates, we can better correct it.

Technology managers, like so many other well-meaning managers, often try to fix the person while ignoring the work environment, even though changing the environment is far more vital for long-term success. Managers who want to avert employee burnout should concentrate their attention and efforts on: Fostering a respectful, supportive work environment that emphasizes learning from failures rather than blaming Communicating a strong sense of purpose Investing in employee development Asking employees what is preventing them from achieving their objectives and then fixing those things Giving employees time, space, and resources to experiment and learn Last but not least, employees must be given the authority to make decisions that affect their work and their jobs, particularly in areas where they are responsible for the outcomes.

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.

After I left finance, I started attending some of the fashionable conferences attended by pre-rich and post-rich technology people and the new category of technology intellectuals. I was initially exhilarated to see them wearing no ties, as, living among tie-wearing abhorrent bankers, I had developed the illusion that anyone who doesn’t wear a tie was not an empty suit. But these conferences, while colorful and slick with computerized images and fancy animations, felt depressing. I knew I did not belong. It was not just their additive approach to the future (failure to subtract the fragile rather than add to destiny). It was not entirely their blindness by uncompromising neomania. It took a while for me to realize the reason: a profound lack of elegance. Technothinkers tend to have an “engineering mind”—to put it less politely, they have autistic tendencies. While they don’t usually wear ties, these types tend, of course, to exhibit all the textbook characteristics of nerdiness—mostly lack of charm, interest in objects instead of persons, causing them to neglect their looks. They love precision at the expense of applicability. And they typically share an absence of literary culture. This absence of literary culture is actually a marker of future blindness because it is usually accompanied by a denigration of history, a byproduct of unconditional neomania. Outside of the niche and isolated genre of science fiction, literature is about the past. We do not learn physics or biology from medieval textbooks, but we still read Homer, Plato, or the very modern Shakespeare. We cannot talk about sculpture without knowledge of the works of Phidias, Michelangelo, or the great Canova. These are in the past, not in the future. Just by setting foot into a museum, the aesthetically minded person is connecting with the elders. Whether overtly or not, he will tend to acquire and respect historical knowledge, even if it is to reject it. And the past—properly handled, as we will see in the next section—is a much better teacher about the properties of the future than the present. To understand the future, you do not need technoautistic jargon, obsession with “killer apps,” these sort of things. You just need the following: some respect for the past, some curiosity about the historical record, a hunger for the wisdom of the elders, and a grasp of the notion of “heuristics,” these often unwritten rules of thumb that are so determining of survival. In other words, you will be forced to give weight to things that have been around, things that have survived.

Intelligent assistance involves leveraging artificial intelligence to enable the government, individual companies, and the nonprofit social sector to develop more sophisticated online and mobile platforms that can empower every worker to engage in lifelong learning on their own time, and to have their learning recognized and rewarded with advancement. Intelligent assistants arise when we use artificial intelligence to improve the interfaces between humans and their tools with software, so humans can not only learn faster but also act faster and act smarter. Lastly, we need to deploy AI to create more intelligent algorithms, or what Reid Hoffman calls “human networks”—so that we can much more efficiently connect people to all the job opportunities that exist, all the skills needed for each job, and all the educational opportunities to acquire those skills cheaply and easily.

So which theory did Lagos believe in? The relativist or the universalist?" "He did not seem to think there was much of a difference. In the end, they are both somewhat mystical. Lagos believed that both schools of thought had essentially arrived at the same place by different lines of reasoning." "But it seems to me there is a key difference," Hiro says. "The universalists think that we are determined by the prepatterned structure of our brains -- the pathways in the cortex. The relativists don't believe that we have any limits." "Lagos modified the strict Chomskyan theory by supposing that learning a language is like blowing code into PROMs -- an analogy that I cannot interpret." "The analogy is clear. PROMs are Programmable Read-Only Memory chips," Hiro says. "When they come from the factory, they have no content. Once and only once, you can place information into those chips and then freeze it -- the information, the software, becomes frozen into the chip -- it transmutes into hardware. After you have blown the code into the PROMs, you can read it out, but you can't write to them anymore. So Lagos was trying to say that the newborn human brain has no structure -- as the relativists would have it -- and that as the child learns a language, the developing brain structures itself accordingly, the language gets 'blown into the hardware and becomes a permanent part of the brain's deep structure -- as the universalists would have it." "Yes. This was his interpretation." "Okay. So when he talked about Enki being a real person with magical powers, what he meant was that Enki somehow understood the connection between language and the brain, knew how to manipulate it. The same way that a hacker, knowing the secrets of a computer system, can write code to control it -- digital namshubs?" "Lagos said that Enki had the ability to ascend into the universe of language and see it before his eyes. Much as humans go into the Metaverse. That gave him power to create nam-shubs. And nam-shubs had the power to alter the functioning of the brain and of the body." "Why isn't anyone doing this kind of thing nowadays? Why aren't there any namshubs in English?" "Not all languages are the same, as Steiner points out. Some languages are better at metaphor than others. Hebrew, Aramaic, Greek, and Chinese lend themselves to word play and have achieved a lasting grip on reality: Palestine had Qiryat Sefer, the 'City of the Letter,' and Syria had Byblos, the 'Town of the Book.' By contrast other civilizations seem 'speechless' or at least, as may have been the case in Egypt, not entirely cognizant of the creative and transformational powers of language. Lagos believed that Sumerian was an extraordinarily powerful language -- at least it was in Sumer five thousand years ago." "A language that lent itself to Enki's neurolinguistic hacking." "Early linguists, as well as the Kabbalists, believed in a fictional language called the tongue of Eden, the language of Adam. It enabled all men to understand each other, to communicate without misunderstanding. It was the language of the Logos, the moment when God created the world by speaking a word. In the tongue of Eden, naming a thing was the same as creating it. To quote Steiner again, 'Our speech interposes itself between apprehension and truth like a dusty pane or warped mirror. The tongue of Eden was like a flawless glass; a light of total understanding streamed through it. Thus Babel was a second Fall.' And Isaac the Blind, an early Kabbalist, said that, to quote Gershom Scholem's translation, 'The speech of men is connected with divine speech and all language whether heavenly or human derives from one source: the Divine Name.' The practical Kabbalists, the sorcerers, bore the title Ba'al Shem, meaning 'master of the divine name.'" "The machine language of the world," Hiro says.

The Xerox Corporation’s Palo Alto Research Center, known as Xerox PARC, had been established in 1970 to create a spawning ground for digital ideas. It was safely located, for better and for worse, three thousand miles from the commercial pressures of Xerox corporate headquarters in Connecticut. Among its visionaries was the scientist Alan Kay, who had two great maxims that Jobs embraced: “The best way to predict the future is to invent it” and “People who are serious about software should make their own hardware.” Kay pushed the vision of a small personal computer, dubbed the “Dynabook,” that would be easy enough for children to use. So Xerox PARC’s engineers began to develop user-friendly graphics that could replace all of the command lines and DOS prompts that made computer screens intimidating. The metaphor they came up with was that of a desktop. The screen could have many documents and folders on it, and you could use a mouse to point and click on the one you wanted to use.

The foundation of your greatness is in your head. Your brain is the most sophisticated computer there is. Its ten billion parts can store the equivalent of one hundred trillion words. It would take dozens of buildings to house computers capable of containing that much information. You have the potential to become a gifted genius, because you were born with the equivalent of a Pentium 10000 processor with hundreds of “cores” and millions of gigabytes of memory. However, like any powerful computer, your brain requires to be turned on and programed properly! Any computer today has more capacity and processing power than all the computers used by NASA to send rockets to the moon. However, you cannot launch rockets from your iPhone (or your Galaxy!) because you don’t have the necessary software (and hopefully nor the rockets...) However, with the right apps, you COULD! It is the same with that amazing computer in your head: You have to turn it on, and then upload the right programs or apps that will allow you to develop your potential and achieve everything you set out to do in life.

Why is programming fun? What delights may its practitioner expect as his reward? First is the sheer joy of making things. As the child delights in his first mud pie, so the adult enjoys building things, especially things of his own design. I think this delight must be an image of God’s delight in making things, a delight shown in the distinctness and newness of each leaf and each snowflake. Second is the pleasure of making things that are useful to other people. Deep within, we want others to use our work and to find it helpful. In this respect the programming system is not essentially different from the child’s first clay pencil holder “for Daddy’s office.” Third is the fascination of fashioning complex puzzle-like objects of interlocking moving parts and watching them work in subtle cycles, playing out the consequences of principles built in from the beginning. The programmed computer has all the fascination of the pinball machine or the jukebox mechanism, carried to the ultimate. Fourth is the joy of always learning, which springs from the nonrepeating nature of the task. In one way or another the problem is ever new, and its solver learns something; sometimes practical, sometimes theoretical, and sometimes both. Finally, there is the delight of working in such a tractable medium. The programmer, like the poet, works only slightly removed from pure thought-stuff. He builds his castles in the air, from air, creating by exertion of the imagination. Few media of creation are so flexible, so easy to polish and rework, so readily capable of realizing grand conceptual structures. (As we shall see later, this very tractability has its own problems.) Yet the program construct, unlike the poet’s words, is real in the sense that it moves and works, producing visible outputs separate from the construct itself. It prints results, draws pictures, produces sounds, moves arms. The magic of myth and legend has come true in our time. One types the correct incantation on a keyboard and a display screen comes to life, showing things that never were nor could be. Programming then is fun because it gratifies creative longings built deep within us and delights sensibilities we have in common with all men.

In the present time, Information Technology has emerged as one of the most promising Industries across the globe. Globally for the reduction of cost, time and efforts involved in the production and supply of the goods and services has made whole business world to adopt the technological support. And due to this reason only Software development have emerged as a important means of growth of IT Industry in India. Software Development Companies in India Have played a crucial role in rapid development of Software industry in India. These Companies Constantly improve and enhance the world of computers and technology. With the help of Software development all the complicated machines whether its computers, laptops, mobile phones or navigation devices all these machines are the way they are today performing various tasks successfully. As Software Development is having a essential role in many industries, so organizations have realized their importance for improving themselves in various aspects of management. Software Development have increased the productivity of the businesses by reducing the human efforts and errors. This increased demand in the Software Development have also given rise to high demand of Software Development Companies everywhere. Even there is a huge demand of best Software Company in Lucknow as Lucknow being capital of U.P have become a growing market for various industries and now almost every offline brand has setup into online businesses of their products and services. As the number of internet users are increasing day by day so are the businesses entering into the online so that they could influence customers online. Besides Software Development many other web solutions like web hosting, web development and website designing services have great demand in the market also therefore, Software Companies have started offering all these services along with software development. Software Industry is flooded with various software companies which are also Website Development Company in Lucknow offering various web based services but it is required by you to choose wisely which company to choose to help your business sustain successfully in long run and stay ahead of its competitors in the market. The company is choosen such that which provide good quality software’s in affordable price.

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.

As the Model S fever gripped Silicon Valley, I visited Ford’s small research and development lab in Palo Alto. The head of the lab at the time was a ponytailed, sandal-wearing engineer named T. J. Giuli, who felt very jealous of Tesla. Inside of every Ford were dozens of computing systems made by different companies that all had to speak to each other and work as one. It was a mess of complexity that had evolved over time, and simplifying the situation would prove near impossible at this point, especially for a company like Ford, which needed to pump out hundreds of thousands of cars per year and could not afford to stop and reboot. Tesla, by contrast, got to start from scratch and make its own software the focus of the Model S. Giuli would have loved the same opportunity. “Software is in many ways the heart of the new vehicle experience,” he said. “From the powertrain to the warning chimes in the car, you’re using software to create an expressive and pleasing environment. The level of integration that the software has into the rest of the Model S is really impressive. Tesla is a benchmark for what we do here.” Not long after this chat, Giuli left Ford to become an engineer at a stealth start-up. There

We had heard rumours of what people referred to as a ‘phantom accounting system’, also called zappers and phantom ware. This phenomenon was unheard of in South Africa at the time. The more formal term used to describe this kind of criminal financial-management software is a ‘sales-suppression system’. The Organisation for Economic Cooperation and Development (OECD), in which South Africa has observer status, issued a guide on these systems in 2013.10 On the surface, the technology seems like a supposedly normal accounting system, used mainly by retailers. It has all the expected features: it records stock, sales, invoices, receipts and taxes. It can print daily, weekly and monthly accounting records. Yet the software has a feature that can blank out certain sales and receipts. You can set it to suppress, for instance, every fourth sale, or random sales of a particular value, whichever you prefer. The effect is that, on paper, your stock, sales and receipts would balance for tax purposes. All you would have to do is click on a secret place on the screen, or type a particular code on the keyboard, and the unrecorded sales and receipts would reflect. One would then be able to take this money out of the company’s takings for the day, week or month, and people would be none the wiser.

a young Goldman Sachs banker named Joseph Park was sitting in his apartment, frustrated at the effort required to get access to entertainment. Why should he trek all the way to Blockbuster to rent a movie? He should just be able to open a website, pick out a movie, and have it delivered to his door. Despite raising around $250 million, Kozmo, the company Park founded, went bankrupt in 2001. His biggest mistake was making a brash promise for one-hour delivery of virtually anything, and investing in building national operations to support growth that never happened. One study of over three thousand startups indicates that roughly three out of every four fail because of premature scaling—making investments that the market isn’t yet ready to support. Had Park proceeded more slowly, he might have noticed that with the current technology available, one-hour delivery was an impractical and low-margin business. There was, however, a tremendous demand for online movie rentals. Netflix was just then getting off the ground, and Kozmo might have been able to compete in the area of mail-order rentals and then online movie streaming. Later, he might have been able to capitalize on technological changes that made it possible for Instacart to build a logistics operation that made one-hour grocery delivery scalable and profitable. Since the market is more defined when settlers enter, they can focus on providing superior quality instead of deliberating about what to offer in the first place. “Wouldn’t you rather be second or third and see how the guy in first did, and then . . . improve it?” Malcolm Gladwell asked in an interview. “When ideas get really complicated, and when the world gets complicated, it’s foolish to think the person who’s first can work it all out,” Gladwell remarked. “Most good things, it takes a long time to figure them out.”* Second, there’s reason to believe that the kinds of people who choose to be late movers may be better suited to succeed. Risk seekers are drawn to being first, and they’re prone to making impulsive decisions. Meanwhile, more risk-averse entrepreneurs watch from the sidelines, waiting for the right opportunity and balancing their risk portfolios before entering. In a study of software startups, strategy researchers Elizabeth Pontikes and William Barnett find that when entrepreneurs rush to follow the crowd into hyped markets, their startups are less likely to survive and grow. When entrepreneurs wait for the market to cool down, they have higher odds of success: “Nonconformists . . . that buck the trend are most likely to stay in the market, receive funding, and ultimately go public.” Third, along with being less recklessly ambitious, settlers can improve upon competitors’ technology to make products better. When you’re the first to market, you have to make all the mistakes yourself. Meanwhile, settlers can watch and learn from your errors. “Moving first is a tactic, not a goal,” Peter Thiel writes in Zero to One; “being the first mover doesn’t do you any good if someone else comes along and unseats you.” Fourth, whereas pioneers tend to get stuck in their early offerings, settlers can observe market changes and shifting consumer tastes and adjust accordingly. In a study of the U.S. automobile industry over nearly a century, pioneers had lower survival rates because they struggled to establish legitimacy, developed routines that didn’t fit the market, and became obsolete as consumer needs clarified. Settlers also have the luxury of waiting for the market to be ready. When Warby Parker launched, e-commerce companies had been thriving for more than a decade, though other companies had tried selling glasses online with little success. “There’s no way it would have worked before,” Neil Blumenthal tells me. “We had to wait for Amazon, Zappos, and Blue Nile to get people comfortable buying products they typically wouldn’t order online.

There are hundreds of examples of highly functioning commons around the world today. Some have been around for centuries, others have risen in response to economic and environmental crises, and still others have been inspired by the distributive bias of digital networks. From the seed-sharing commons of India to the Potato Park of Peru, indigenous populations have been maintaining their lands and managing biodiversity through a highly articulated set of rules about sharing and preservation. From informal rationing of parking spaces in Boston to Richard Stallman’s General Public License (GPL) for software, new commons are serving to reinstate the value of land and labor, as well as the ability of people to manage them better than markets can. In the 1990s, Elinor Ostrom, the American political scientist most responsible for reviving serious thought about commoning, studied what specifically makes a commons successful. She concluded that a commons must have an evolving set of rules about access and usage and that it must have a way of punishing transgressions. It must also respect the particular character of the resource being managed and the people who have worked with that resource the longest. Managing a fixed supply of minerals is different from managing a replenishing supply of timber. Finally, size and place matter. It’s easier for a town to manage its water supply than for the planet to establish water-sharing rules.78 In short, a commons must be bound by people, place, and rules. Contrary to prevailing wisdom, it’s not an anything-goes race to the bottom. It is simply a recognition of boundaries and limits. It’s pooled, multifaceted investment in pursuit of sustainable production. It is also an affront to the limitless expansion sought by pure capital. If anything, the notion of a commons’ becoming “enclosed” by privatization is a misnomer: privatizing a commons breaks the boundaries that protected its land and labor from pure market forces. For instance, the open-source seed-sharing networks of India promote biodiversity and fertilizer-free practices among farmers who can’t afford Western pesticides.79 They have sustained themselves over many generations by developing and adhering to a complex set of rules about how seed species are preserved, as well as how to mix crops on soil to recycle its nutrients over centuries of growing. Today, they are in battle with corporations claiming patents on these heirloom seeds and indigenous plants. So it’s not the seed commons that have been enclosed by the market at all; rather, the many-generations-old boundaries have been penetrated and dissolved by disingenuously argued free-market principles.

A great deal of effort has been devoted to explaining Babel. Not the Babel event -- which most people consider to be a myth -- but the fact that languages tend to diverge. A number of linguistic theories have been developed in an effort to tie all languages together." "Theories Lagos tried to apply to his virus hypothesis." "Yes. There are two schools: relativists and universalists. As George Steiner summarizes it, relativists tend to believe that language is not the vehicle of thought but its determining medium. It is the framework of cognition. Our perceptions of everything are organized by the flux of sensations passing over that framework. Hence, the study of the evolution of language is the study of the evolution of the human mind itself." "Okay, I can see the significance of that. What about the universalists?" "In contrast with the relativists, who believe that languages need not have anything in common with each other, the universalists believe that if you can analyze languages enough, you can find that all of them have certain traits in common. So they analyze languages, looking for such traits." "Have they found any?" "No. There seems to be an exception to every rule." "Which blows universalism out of the water." "Not necessarily. They explain this problem by saying that the shared traits are too deeply buried to be analyzable." "Which is a cop out." "Their point is that at some level, language has to happen inside the human brain. Since all human brains are more or less the same --" "The hardware's the same. Not the software." "You are using some kind of metaphor that I cannot understand." "Well, a French-speaker's brain starts out the same as an English-speaker's brain. As they grow up, they get programmed with different software -- they learn different languages." "Yes. Therefore, according to the universalists, French and English -- or any other languages -- must share certain traits that have their roots in the 'deep structures' of the human brain. According to Chomskyan theory, the deep structures are innate components of the brain that enable it to carry out certain formal kinds of operations on strings of symbols. Or, as Steiner paraphrases Emmon Bach: These deep structures eventually lead to the actual patterning of the cortex with its immensely ramified yet, at the same time, 'programmed' network of electrochemical and neurophysiological channels." "But these deep structures are so deep we can't even see them?" "The universalists place the active nodes of linguistic life -- the deep structures -- so deep as to defy observation and description. Or to use Steiner's analogy: Try to draw up the creature from the depths of the sea, and it will disintegrate or change form grotesquely.

QuickBooks Tech Support +1-877-788-4840 QuickBooks is designed and developed by intuit. QuickBooks is a good customer service provider software. If you are a customer of QuickBooks and you want credit from QuickBooks then you can easily get your credit from QuickBooks. It is an online process. To complete this process firstly go to QuickBooks Software where you installed that software. But this facility provides only those customers who are the permanent or valuable customers of QuickBooks. Before doing this you need to know the difference between refund and credit. Choose the right option which you want to use QuickBooks Accounting Software. Refund is the process when the amount is returned to the customer account. But this refund has many terms and conditions. If your request is really legal or genuine. If these conditions are fulfilled then QuickBooks refunds you. But in a credit case when you want to reduce the amount from your actual amount. Terms and conditions also apply in this case. If you want more information regarding QuickBooks credit related. You can contact our highly proficient QuickBooks Help Professional. They give you a satisfied resolution. Our QuickBooks Helpline number is+1-877-788-4840. You can choose unlimited chat for one week trial membership, you can cancel this chat process any time. Here, we are discussing different QuickBooks Support tools that perform the different functionality i.e. working of each tool is different or separate from one another. These tools are provided to resolve certain types of common problems that are needed to be encountered.

What Musk had done that the rival automakers missed or didn’t have the means to combat was turn Tesla into a lifestyle. It did not just sell someone a car. It sold them an image, a feeling they were tapping into the future, a relationship. Apple did the same thing decades ago with the Mac and then again with the iPod and iPhone. Even those who were not religious about their affiliation to Apple were sucked into its universe once they bought the hardware and downloaded software like iTunes. This sort of relationship is hard to pull off if you don’t control as much of the lifestyle as possible. PC makers that farmed their software out to Microsoft, their chips to Intel, and their design to Asia could never make machines as beautiful and as complete as Apple’s. They also could not respond in time as Apple took this expertise to new areas and hooked people on its applications. You can see Musk’s embrace of the car as lifestyle in Tesla’s abandonment of model years. Tesla does not designate cars as being 2014s or 2015s, and it also doesn’t have “all the 2014s in stock must go, go, go and make room for the new cars” sales. It produces the best Model S it can at the time, and that’s what the customer receives. This means that Tesla does not develop and hold on to a bunch of new features over the course of the year and then unleash them in a new model all at once. It adds features one by one to the manufacturing line when they’re ready. Some customers may be frustrated to miss out on a feature here and there. Tesla, however, manages to deliver most of the upgrades as software updates that everyone gets, providing current Model S owners with pleasant surprises.

#1. No Escape and feature keys Today’s Apple Event confirmed many of the rumors surrounding the lengthy-awaited refresh of the Macbook Pro line. The Escape and Function keys at the laptops had been deserted in choose of a hint bar that changed relying at the software that is getting used. The last the Macbook Pro got a chief update was a shocking 4 years in the past and many guides are celebrating the brand new design. However, the lack of bodily Escape and Function keys is a disaster for one major set of Apple’s customers — Developers. Let’s test numbers: There are ~ 19 million developers inside the global. And Apple has managed to promote ~19 million Macs over the past four quarters. What a twist of fate! Yes, builders are drawn toward Apple products mainly for software program reasons: the Unix-like running gadget and the proprietary development atmosphere. But builders want to have a useful keyboard to make use of that software and now they don’t. Why Tim Cook, why? This isn’t to say that the contact bar is an inherently awful concept. You should locate it on pinnacle of the Esc and feature keys as opposed to doing away with them completely! Something like this: #2 Power. Almost no improvement for RAM and a processor The 2016 MacBook Pro ships with RAM and processor specifications that are nearly equal to the 2010 model. Deja vu? RAM: At least it appears like that, because the MacBook Pro has had alternatives of as much as 16 GB of RAM in view that 2010. The best difference now's that you pay for the update. Processors: The MacBook Pro had options with 2.4 gigahertz twin-middle processors again in 2010. Anything new in 2016? Not absolutely, well… nope.

Similarly, the computers used to run the software on the ground for the mission were borrowed from a previous mission. These machines were so out of date that Bowman had to shop on eBay to find replacement parts to get the machines working. As systems have gone obsolete, JPL no longer uses the software, but Bowman told me that the people on her team continue to use software built by JPL in the 1990s, because they are familiar with it. She said, “Instead of upgrading to the next thing we decided that it was working just fine for us and we would stay on the platform.” They have developed so much over such a long period of time with the old software that they don’t want to switch to a newer system. They must adapt to using these outdated systems for the latest scientific work. Working within these constraints may seem limiting. However, building tools with specific constraints—from outdated technologies and low bitrate radio antennas—can enlighten us. For example, as scientists started to explore what they could learn from the wait times while communicating with deep space probes, they discovered that the time lag was extraordinarily useful information. Wait times, they realized, constitute an essential component for locating a probe in space, calculating its trajectory, and accurately locating a target like Pluto in space. There is no GPS for spacecraft (they aren’t on the globe, after all), so scientists had to find a way to locate the spacecraft in the vast expanse. Before 1960, the location of planets and objects in deep space was established through astronomical observation, placing an object like Pluto against a background of stars to determine its position.15 In 1961, an experiment at the Goldstone Deep Space Communications Complex in California used radar to more accurately define an “astronomical unit” and help measure distances in space much more accurately.16 NASA used this new data as part of creating the trajectories for missions in the following years. Using the data from radio signals across a wide range of missions over the decades, the Deep Space Network maintained an ongoing database that helped further refine the definition of an astronomical unit—a kind of longitudinal study of space distances that now allows missions like New Horizons to create accurate flight trajectories. The Deep Space Network continued to find inventive ways of using the time lag of radio waves to locate objects in space, ultimately finding that certain ways of waiting for a downlink signal from the spacecraft were less accurate than others. It turned to using the antennas from multiple locations, such as Goldstone in California and the antennas in Canberra, Australia, or Madrid, Spain, to time how long the signal took to hit these different locations on Earth. The time it takes to receive these signals from the spacecraft works as a way to locate the probes as they are journeying to their destination. Latency—or the different time lag of receiving radio signals on different locations of Earth—is the key way that deep space objects are located as they journey through space. This discovery was made possible during the wait times for communicating with these craft alongside the decades of data gathered from each space mission. Without the constraint of waiting, the notion of using time as a locating feature wouldn’t have been possible.

It's not that we're dumb. On the contrary, many millions of people have exerted great intelligence and creativity in building the modern world. It's more that we're being swept into unknown and dangerous waters by accelerating economic growth. On just one single day of the days I have spent writing this book, as much world trade was carried out as in the whole of 1949; as much scientific research was published as in the whole of 1960; as many telephone calls were made as in all of 1983; as many e-mails were sent as in 1990.11 Our natural, human, and industrial systems, which evolve slowly, are struggling to adapt. Laws and institutions that we might expect to regulate these flows have not been able to keep up. A good example is what is inaccurately described as mindless sprawl in our physical environment. We deplore the relentless spread of low-density suburbs over millions of acres of formerly virgin land. We worry about its environmental impact, about the obesity in people that it fosters, and about the other social problems that come in its wake. But nobody seems to have designed urban sprawl, it just happens-or so it appears. On closer inspection, however, urban sprawl is not mindless at all. There is nothing inevitable about its development. Sprawl is the result of zoning laws designed by legislators, low-density buildings designed by developers, marketing strategies designed by ad agencies, tax breaks designed by economists, credit lines designed by banks, geomatics designed by retailers, data-mining software designed by hamburger chains, and automobiles designed by car designers. The interactions between all these systems and human behavior are complicated and hard to understand-but the policies themselves are not the result of chance. "Out of control" is an ideology, not a fact.

Computers speak machine language," Hiro says. "It's written in ones and zeroes -- binary code. At the lowest level, all computers are programmed with strings of ones and zeroes. When you program in machine language, you are controlling the computer at its brainstem, the root of its existence. It's the tongue of Eden. But it's very difficult to work in machine language because you go crazy after a while, working at such a minute level. So a whole Babel of computer languages has been created for programmers: FORTRAN, BASIC, COBOL, LISP, Pascal, C, PROLOG, FORTH. You talk to the computer in one of these languages, and a piece of software called a compiler converts it into machine language. But you never can tell exactly what the compiler is doing. It doesn't always come out the way you want. Like a dusty pane or warped mirror. A really advanced hacker comes to understand the true inner workings of the machine -- he sees through the language he's working in and glimpses the secret functioning of the binary code -- becomes a Ba'al Shem of sorts." "Lagos believed that the legends about the tongue of Eden were exaggerated versions of true events," the Librarian says. "These legends reflected nostalgia for a time when people spoke Sumerian, a tongue that was superior to anything that came afterward." "Is Sumerian really that good?" "Not as far as modern-day linguists can tell," the Librarian says. "As I mentioned, it is largely impossible for us to grasp. Lagos suspected that words worked differently in those days. If one's native tongue influences the physical structure of the developing brain, then it is fair to say that the Sumerians -- who spoke a language radically different from anything in existence today -- had fundamentally different brains from yours. Lagos believed that for this reason, Sumerian was a language ideally suited to the creation and propagation of viruses. That a virus, once released into Sumer, would spread rapidly and virulently, until it had infected everyone." "Maybe Enki knew that also," Hiro says. "Maybe the nam-shub of Enki wasn't such a bad thing. Maybe Babel was the best thing that ever happened to us.

Like any place in Reality, the Street is subject to development. Developers can build their own small streets feeding off of the main one. They can build buildings, parks, signs, as well as things that do not exist in Reality, such as vast hovering overhead light shows, special neighborhoods where the rules of three-dimensional spacetime are ignored, and free-combat zones where people can go to hunt and kill each other. The only difference is that since the Street does not really exist -- it's just a computer-graphics protocol written down on a piece of paper somewhere -- none of these things is being physically built. They are, rather, pieces of software, made available to the public over the worldwide fiber-optics network. When Hiro goes into the Metaverse and looks down the Street and sees buildings and electric signs stretching off into the darkness, disappearing over the curve of the globe, he is actually staring at the graphic representations -- the user interfaces -- of a myriad different pieces of software that have been engineered by major corporations. In order to place these things on the Street, they have had to get approval from the Global Multimedia Protocol Group, have had to buy frontage on the Street, get zoning approval, obtain permits, bribe inspectors, the whole bit. The money these corporations pay to build things on the Street all goes into a trust fund owned and operated by the GMPG, which pays for developing and expanding the machinery that enables the Street to exist. Hiro has a house in a neighborhood just off the busiest part of the Street. it is a very old neighborhood by Street standards. About ten years ago, when the Street protocol was first written, Hiro and some of his buddies pooled their money and bought one of the first development licenses, created a little neighborhood of hackers. At the time, it was just a little patchwork of light amid a vast blackness. Back then, the Street was just a necklace of streetlights around a black ball in space. Since then, the neighborhood hasn't changed much, but the Street has. By getting in on it early, Hiro's buddies got a head start on the whole business. Some of them even got very rich off of it. That's why Hiro has a nice big house in the Metaverse but has to share a 20-by- 30 in Reality. Real estate acumen does not always extend across universes.

[A] central theme is why social, political, and economic institutions tend to coevolve in a manner that reinforces rather than undermines one another. The welfare state is not 'politics against markets,' as commonly assumed, but politics with markets. Although it is popular to think that markets, especially global ones, interfere with the welfare state, and vice versa, this notion is simply inconsistent with the postwar record of actual welfare state development. The United States, which has a comparatively small welfare state and flexible labor markets, has performed well in terms of jobs and growth during the past two decades; however, before then the countries with the largest welfare states and the most heavily regulated labor markets exceeded those in the United States on almost any gauge of economic competitiveness and performance. Despite the change in economic fortunes, the relationship between social protection and product market strategies continues to hold. Northern Europe and Japan still dominate high-quality markets for machine tools and consumer durables, whereas the United States dominates software, biotech, and other high-tech industries. There is every reason that firms and governments will try to preserve the institutions that give rise to these comparative advantages, and here the social protection system (broadly construed to include job security and protection through the industrial relations system) plays a key role. The reason is that social insurance shapes the incentives workers and firms have for investing in particular types of skills, and skills are critical for competitive advantage in human-capital-intensive economies. Firms do not develop competitive advantages in spite of systems of social protection, but because of it. Continuing this line of argument, the changing economic fortunes of different welfare production regimes probably has very little to do with growing competitive pressure from the international economy. To the contrary, it will be argued in Chapter 6 that the main problem for Europe is the growing reliance on services that have traditionally been closed to trade. In particular, labor-intensive, low-productivity jobs do not thrive in the context of high social protection and intensive labor-market regulation, and without international trade, countries cannot specialize in high value-added services. Lack of international trade and competition, therefore, not the growth of these, is the cause of current employment problems in high-protection countries.