Engineering Project Management Quotes

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

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

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.

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

you only get value from projects when they finish: to make progress, above all else, you must ensure that some of your projects finish.

In his excitement, Jobs began to take over the daily management of the Lisa project, which was being run by John Couch, the former HP engineer.

There can be no question that Musk has mastered the art of getting the most out of his employees. Interview three dozen SpaceX engineers and each one of them will have picked up on a managerial nuance that Musk has used to get people to meet his deadlines. One example from Brogan: Where a typical manager may set the deadline for the employee, Musk guides his engineers into taking ownership of their own delivery dates. “He doesn’t say, ‘You have to do this by Friday at two P.M.,’” Brogan said. “He says, ‘I need the impossible done by Friday at two P.M. Can you do it?’ Then, when you say yes, you are not working hard because he told you to. You’re working hard for yourself. It’s a distinction you can feel. You have signed up to do your own work.” And by recruiting hundreds of bright, self-motivated people, SpaceX has maximized the power of the individual. One person putting in a sixteen-hour day ends up being much more effective than two people working eight-hour days together. The individual doesn’t have to hold meetings, reach a consensus, or bring other people up to speed on a project. He just keeps working and working and working. The ideal SpaceX employee is someone like Steve Davis, the director of advanced projects at SpaceX. “He’s been working sixteen hours a day every day for years,” Brogan said. “He gets more done than eleven people working together.

Adopting a remote, managerial point of view, you could say that the Eagle project was a case where a local system of management worked as it should: competition for resources creating within a team inside a company an entrepreneurial spirit, which was channeled in the right direction by constraints sent down from the top. But it seems more accurate to say that a group of engineers got excited about building a computer. Whether it arose by corporate bungling or by design, the opportunity had to be grasped.

Good engineering estimates are possible only if you have two things: good information and good engineers. If the specs are crap, and a programmer is asked to conjure up a number based on an incomprehensible whiteboard scribbling, everyone should know exactly what they’re getting: a fuzzy scribble of an estimate.

Entrepreneurs who kept their day jobs had 33 percent lower odds of failure than those who quit. If you’re risk averse and have some doubts about the feasibility of your ideas, it’s likely that your business will be built to last. If you’re a freewheeling gambler, your startup is far more fragile. Like the Warby Parker crew, the entrepreneurs whose companies topped Fast Company’s recent most innovative lists typically stayed in their day jobs even after they launched. Former track star Phil Knight started selling running shoes out of the trunk of his car in 1964, yet kept working as an accountant until 1969. After inventing the original Apple I computer, Steve Wozniak started the company with Steve Jobs in 1976 but continued working full time in his engineering job at Hewlett-Packard until 1977. And although Google founders Larry Page and Sergey Brin figured out how to dramatically improve internet searches in 1996, they didn’t go on leave from their graduate studies at Stanford until 1998. “We almost didn’t start Google,” Page says, because we “were too worried about dropping out of our Ph.D. program.” In 1997, concerned that their fledgling search engine was distracting them from their research, they tried to sell Google for less than $2 million in cash and stock. Luckily for them, the potential buyer rejected the offer. This habit of keeping one’s day job isn’t limited to successful entrepreneurs. Many influential creative minds have stayed in full-time employment or education even after earning income from major projects. Selma director Ava DuVernay made her first three films while working in her day job as a publicist, only pursuing filmmaking full time after working at it for four years and winning multiple awards. Brian May was in the middle of doctoral studies in astrophysics when he started playing guitar in a new band, but he didn’t drop out until several years later to go all in with Queen. Soon thereafter he wrote “We Will Rock You.” Grammy winner John Legend released his first album in 2000 but kept working as a management consultant until 2002, preparing PowerPoint presentations by day while performing at night. Thriller master Stephen King worked as a teacher, janitor, and gas station attendant for seven years after writing his first story, only quitting a year after his first novel, Carrie, was published. Dilbert author Scott Adams worked at Pacific Bell for seven years after his first comic strip hit newspapers. Why did all these originals play it safe instead of risking it all?

We became the most successful advanced projects company in the world by hiring talented people, paying them top dollar, and motivating them into believing that they could produce a Mach 3 airplane like the Blackbird a generation or two ahead of anybody else. Our design engineers had the keen experience to conceive the whole airplane in their mind’s-eye, doing the trade-offs in their heads between aerodynamic needs and weapons requirements. We created a practical and open work environment for engineers and shop workers, forcing the guys behind the drawing boards onto the shop floor to see how their ideas were being translated into actual parts and to make any necessary changes on the spot. We made every shop worker who designed or handled a part responsible for quality control. Any worker—not just a supervisor or a manager—could send back a part that didn’t meet his or her standards. That way we reduced rework and scrap waste. We encouraged our people to work imaginatively, to improvise and try unconventional approaches to problem solving, and then got out of their way. By applying the most commonsense methods to develop new technologies, we saved tremendous amounts of time and money, while operating in an atmosphere of trust and cooperation both with our government customers and between our white-collar and blue-collar employees. In the end, Lockheed’s Skunk Works demonstrated the awesome capabilities of American inventiveness when free to operate under near ideal working conditions. That may be our most enduring legacy as well as our source of lasting pride.

The capability of self-organizing teams lies in collaboration. When two engineers scratch out a design on a whiteboard, they are collaborating. When team members meet to brainstorm a design, they are collaborating. When team leaders meet to decide whether a product is ready to ship, they are collaborating. The result of any collaboration can be categorized as a tangible deliverable, a decision, or shared knowledge.

Adopting a remote, managerial point of view, you could say that the Eagle project was a case where a local system of management worked as it should: competition for resources creating within a team inside a company an entrepreneurial spirit, which was channeled in the right direction by constraints sent down from the top. But it seems more accurate to say that a group of engineers got excited about building a computer.

Trust metrics over intuition. You should have a way to measure every project. Quality is a complex system, the sort of place where your intuition can easily deceive you. Similarly, as you become more senior at your company, your experience will no longer reflect most other folks’ experiences. You already know about the rough edges, and you’ll be the first person in line to get help if you find a new one, but most other folks don’t. Metrics keep you honest.

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

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

How long will the Gilgamesh Project – the quest for immortality – take to complete? A hundred years? Five hundred years? A thousand years? When we recall how little we knew about the human body in 1900, and how much knowledge we have gained in a single century, there is cause for optimism. Genetic engineers have recently managed to double the average life expectancy of Caenorhabditis elegans worms.12 Could they do the same for Homo sapiens? Nanotechnology experts are developing a bionic immune system composed of millions of nano-robots, who would inhabit our bodies, open blocked blood vessels, fight viruses and bacteria, eliminate cancerous cells and even reverse ageing processes.13 A few serious scholars suggest that by 2050, some humans will become a-mortal (not immortal, because they could still die of some accident, but a-mortal, meaning that in the absence of fatal trauma their lives could be extended indefinitely). Whether or not Project Gilgamesh succeeds, from a historical perspective it is fascinating to see that most late-modern religions and ideologies have already taken death and the afterlife out of the equation. Until the eighteenth century, religions considered death and its aftermath central to the meaning of life. Beginning in the eighteenth century, religions and ideologies such as liberalism, socialism and feminism lost all interest in the afterlife. What, exactly, happens to a Communist after he or she dies? What happens to a capitalist? What happens to a feminist? It is pointless to look for the answer in the writings of Marx, Adam Smith or Simone de Beauvoir. The only modern ideology that still awards death a central role is nationalism. In its more poetic and desperate moments, nationalism promises that whoever dies for the nation will for ever live in its collective memory. Yet this promise is so fuzzy that even most nationalists do not really know what to make of it. The

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.

Jack coughed slightly and offered his hand. “Hi, uh. I’m Jack.” Kim took it. “Jack what?” “Huh?” “Your last name, silly.” “Jackson.” She blinked at him. “Your name is Jack Jackson?” He blushed. “No, uh, my first name’s Rhett, but I hate it, so…” He gestured to the chair and she sat. Her dress rode up several inches, exposing pleasing long lines of creamy skin. “Well, Jack, what’s your field of study?” “Biological Engineering, Genetics, and Microbiology. Post-doc. I’m working on a research project at the institute.” “Really? Oh, uh, my apple martini’s getting a little low.” “I’ve got that, one second.” He scurried to the bar and bought her a fresh one. She sipped and managed to make it look not only seductive but graceful as well. “What do you want to do after you’re done with the project?” Kim continued. “Depends on what I find.” She sent him a simmering smile. “What are you looking for?” Immediately, Jack’s eyes lit up and his posture straightened. “I started the project with the intention of learning how to increase the reproduction of certain endangered species. I had interest in the idea of cloning, but it proved too difficult based on the research I compiled, so I went into animal genetics and cellular biology. It turns out the animals with the best potential to combine genes were reptiles because their ability to lay eggs was a smoother transition into combining the cells to create a new species, or one with a similar ancestry that could hopefully lead to rebuilding extinct animals via surrogate birth or in-vitro fertilization. We’re on the edge of breaking that code, and if we do, it would mean that we could engineer all kinds of life and reverse what damage we’ve done to the planet’s ecosystem.” Kim stared. “Right. Would you excuse me for a second?” She wiggled off back to her pack of friends by the bar. Judging by the sniggering and the disgusted glances he was getting, she wasn’t coming back. Jack sighed and finished off his beer, massaging his forehead. “Yes, brilliant move. You blinded her with science. Genius, Jack.” He ordered a second one and finished it before he felt smallish hands on his shoulders and a pair of soft lips on his cheek. He turned to find Kamala had returned, her smile unnaturally bright in the black lights glowing over the room. “So…how did it go with Kim?” He shot her a flat look. “You notice the chair is empty.” Kamala groaned. “You talked about the research project, didn’t you?” “No!” She glared at him. “…maybe…” “You’re so useless, Jack.” She paused and then tousled his hair a bit. “Cheer up. The night’s still young. I’m not giving up on you.” He smiled in spite of himself. “Yet.” Her brown eyes flashed. “Never.

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

This new religion has had a decisive influence on the development of modern science, too. Scientific research is usually funded by either governments or private businesses. When capitalist governments and businesses consider investing in a particular scientific project, the first questions are usually, ‘Will this project enable us to increase production and profits? Will it produce economic growth?’ A project that can’t clear these hurdles has little chance of finding a sponsor. No history of modern science can leave capitalism out of the picture. Conversely, the history of capitalism is unintelligible without taking science into account. Capitalism’s belief in perpetual economic growth flies in the face of almost everything we know about the universe. A society of wolves would be extremely foolish to believe that the supply of sheep would keep on growing indefinitely. The human economy has nevertheless managed to keep on growing throughout the modern era, thanks only to the fact that scientists come up with another discovery or gadget every few years – such as the continent of America, the internal combustion engine, or genetically engineered sheep. Banks and governments print money, but ultimately, it is the scientists who foot the bill.

On November 3, 2015, the day after the Trump Organization transmitted the LOI, Sater emailed Cohen suggesting that the Trump Moscow project could be used to increase candidate Trump's chances at being elected, writing: Buddy our boy can become President of the USA and we can engineer it. I will get all of Putins team to buy in on this, I will manage this process. . . . Michael, Putin gets on stage with Donald for a ribbon cutting for Trump Moscow, and Donald owns the republican nomination. And possibly beats Hillary and our boy is in.... We will manage this process better than anyone. You and I will get Donald and Vladimir on a stage together very shortly. That the game changer.327 Later that day, Sater followed up: Donald doesn't stare down, he negotiates and understands the economic issues and Putin only want to deal with a pragmatic leader, and a successful business man is a good candidate for someone who knows how to negotiate. "Business, politics, whatever it all is the same for someone who knows how to deal" I think I can get Putin to say that at the Trump Moscow press conference. If he says it we own this election. Americas most difficult adversary agreeing that Donald is a good guy to negotiate. . . . We can own this election. Michael my next steps are very sensitive with Putins very very close people, we can pull this off. Michael lets go. 2 boys from Brooklyn getting a USA president elected. This is good really good.328

Professional Bio of Shahin Shardi, P.Eng. Materials Engineer Welding and Pressure Equipment Inspector, QA/QC Specialist Shahin Shardi is a Materials Engineer with experience in integrity management, inspection of pressure equipment, quality control/assurance of large scale oil and gas projects and welding inspection. He stared his career in trades which helped him understand fundamentals of operation of a construction site and execution of large scale projects. This invaluable experience provided him with boots on the ground perspective of requirements of running a successful project and job site. After obtaining an engineering degree from university of British Columbia, he started a career in asset integrity management for oil and gas facilities and inspection of pressure equipment in Alberta, Canada. He has been involved with numerus maintenance shutdowns at various facilities providing engineering support to the maintenance, operations and project personnel regarding selection, repair, maintenance, troubleshooting and long term reliability of equipment. In addition he has extensive experience in area of quality control and assurance of new construction activities in oil and gas industry. He has performed Owner’s Inspector and welding inspector roles in this area. Shahin has extensively applied industry codes of constructions such as ASME Pressure Vessel Code (ASME VIII), Welding (ASME IX), Process Piping (ASME B31.3), Pipe Flanges (ASME B16.5) and various pressure equipment codes and standards. Familiarity with NDT techniques like magnetic particle, liquid penetrant, eddy current, ultrasonic and digital radiography is another valuable knowledge base gained during various projects. Some of his industry certificates are CWB Level 2 Certified Welding Inspector, API 510 Pressure Vessel Inspector, Alberta ABSA In-Service Pressure Vessel Inspector and Saskatchewan TSASK Pressure Equipment Inspector. Shahin is a professional member of Association of Professional Engineers and Geoscientists of Alberta.

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

Manage Your Team’s Collective Time Time management is a group endeavor. The payoff goes far beyond morale and retention. ILLUSTRATION: JAMES JOYCE by Leslie Perlow | 1461 words Most professionals approach time management the wrong way. People who fall behind at work are seen to be personally failing—just as people who give up on diet or exercise plans are seen to be lacking self-control or discipline. In response, countless time management experts focus on individual habits, much as self-help coaches do. They offer advice about such things as keeping better to-do lists, not checking e-mail incessantly, and not procrastinating. Of course, we could all do a better job managing our time. But in the modern workplace, with its emphasis on connectivity and collaboration, the real problem is not how individuals manage their own time. It’s how we manage our collective time—how we work together to get the job done. Here is where the true opportunity for productivity gains lies. Nearly a decade ago I began working with a team at the Boston Consulting Group to implement what may sound like a modest innovation: persuading each member to designate and spend one weeknight out of the office and completely unplugged from work. The intervention was aimed at improving quality of life in an industry that’s notorious for long hours and a 24/7 culture. The early returns were positive; the initiative was expanded to four teams of consultants, and then to 10. The results, which I described in a 2009 HBR article, “Making Time Off Predictable—and Required,” and in a 2012 book, Sleeping with Your Smartphone , were profound. Consultants on teams with mandatory time off had higher job satisfaction and a better work/life balance, and they felt they were learning more on the job. It’s no surprise, then, that BCG has continued to expand the program: As of this spring, it has been implemented on thousands of teams in 77 offices in 40 countries. During the five years since I first reported on this work, I have introduced similar time-based interventions at a range of companies—and I have come to appreciate the true power of those interventions. They put the ownership of how a team works into the hands of team members, who are empowered and incentivized to optimize their collective time. As a result, teams collaborate better. They streamline their work. They meet deadlines. They are more productive and efficient. Teams that set a goal of structured time off—and, crucially, meet regularly to discuss how they’ll work together to ensure that every member takes it—have more open dialogue, engage in more experimentation and innovation, and ultimately function better. CREATING “ENHANCED PRODUCTIVITY” DAYS One of the insights driving this work is the realization that many teams stick to tried-and-true processes that, although familiar, are often inefficient. Even companies that create innovative products rarely innovate when it comes to process. This realization came to the fore when I studied three teams of software engineers working for the same company in different cultural contexts. The teams had the same assignments and produced the same amount of work, but they used very different methods. One, in Shenzen, had a hub-and-spokes org chart—a project manager maintained control and assigned the work. Another, in Bangalore, was self-managed and specialized, and it assigned work according to technical expertise. The third, in Budapest, had the strongest sense of being a team; its members were the most versatile and interchangeable. Although, as noted, the end products were the same, the teams’ varying approaches yielded different results. For example, the hub-and-spokes team worked fewer hours than the others, while the most versatile team had much greater flexibility and control over its schedule. The teams were completely unaware that their counterparts elsewhere in the world were managing their work differently. My research provide

Lastly the corporate office design Gauteng will also require to be planned with particular furniture and tools requirements in mind. It is also important to consideration on sufficient working spaces. Interior office design has turned a little more complex as compare than interior design for residential assignments. This article is all about corporate interiors and project management Gauteng. Interior Office design Floor plans The interior floor plan for an office is first task for space planning. It require skill as well as good creativity for problem solving ability but also special facts of building sets as well as information of the company's needs who will dwell there, normally known as the client as well as tenant. Here the floor plan layout requires to meet all the companies obligations such as how many offices, meeting rooms and storage areas among others and also forces with the applicable regulations as well as standards. The floor plan will also include office designs for different technical and engineering services which include: • Electrical plans for lighting and power • Services designs for Emergency such as exit signs, emergency lighting and mass departure warning methods • Designs related to communications services including phones and computers • Designs related to Fire sprinklers of fire recognition systems and also flames hose reels • Air conditioning Designs • Plumbing services Designs • Designs for safety and entry control systems The corporate interiors and project management needs to be planned with keeping in mind not only all the standards necessary but also the needs of the client's requirements. Office re fit is a general good design perform for work flow and helpful working environments. • Finding the amount of offices, conference rooms and release plan workstations obligatory by the client. • Finding sufficient normal facilities which include storage areas, filing areas, printing areas, and staff facilities including kitchens and toilet facilities. • Office layout for right sitting of offices and workstation work areas to take full advantage of entry to natural light. • Concern of main workflow spaces and flow corridors. • Site of public areas including the reception as well as meeting rooms to keep away from disturbance to the common office work areas. • Area of heavy load luggage compartment systems to make sure structural uprightness of the floor. • Right area for break out as well as staff relaxation areas. • Correct furniture and tools planning

An early lesson I learned in my career was that whenever a large organization attempts to do anything, it always comes down to a single person who can delay the entire project. An engineer might get stuck waiting for a decision or a manager may think she doesn’t have authority to make a critical purchase. These small, seemingly minor hesitations can cause fatal delays.

Increasingly, product developers roll out what’s known as a minimum viable product (MVP).6 An MVP accomplishes the goal of the customer—it tracks your exercise, cooks your food, or monitors your blood sugar—with services and some style, to support the higher price tag it carries. Companies that ship MVPs know that they will improve them and that ideas for those improvements will be generated from the people who first use the product. As Stefan Olander, vice president and general manager of digital sport at Nike, puts it “Get going. Then get better.”7 Software development for websites and applications is undergoing a revolution, from huge complex projects and infrequent releases to the continuous, agile development cycles happening now.

factory automation services Our company majorly dedicated to serving clients having biodiesel plants. Our company has more than 60 engineers who are highly experienced and proficient. Moreover, all our professionals are expertise in different niche such as electrical, process, application, project, mechanical, chemical, civil, structural and controls too. Our professionals do the best possible job to ensure a favorable outcome. For factory automation services, we build and maintain the biodiesel plant. In this context, our experts follow the biodiesel plant construction standards that include plant size determination, selecting an appropriate site, permitting, biodiesel plant engineering, determining your equipment needs, assistance which plant installation, quality and BQ-9000 considerations, plant start up and training, plant management and planning for the future.

Minsky was an ardent supporter of the Cyc project, the most notorious failure in the history of AI. The goal of Cyc was to solve AI by entering into a computer all the necessary knowledge. When the project began in the 1980s, its leader, Doug Lenat, confidently predicted success within a decade. Thirty years later, Cyc continues to grow without end in sight, and commonsense reasoning still eludes it. Ironically, Lenat has belatedly embraced populating Cyc by mining the web, not because Cyc can read, but because there’s no other way. Even if by some miracle we managed to finish coding up all the necessary pieces, our troubles would be just beginning. Over the years, a number of research groups have attempted to build complete intelligent agents by putting together algorithms for vision, speech recognition, language understanding, reasoning, planning, navigation, manipulation, and so on. Without a unifying framework, these attempts soon hit an insurmountable wall of complexity: too many moving parts, too many interactions, too many bugs for poor human software engineers to cope with. Knowledge engineers believe AI is just an engineering problem, but we have not yet reached the point where engineering can take us the rest of the way. In 1962, when Kennedy gave his famous moon-shot speech, going to the moon was an engineering problem. In 1662, it wasn’t, and that’s closer to where AI is today. In industry, there’s no sign that knowledge engineering will ever be able to compete with machine learning outside of a few niche areas. Why pay experts to slowly and painfully encode knowledge into a form computers can understand, when you can extract it from data at a fraction of the cost? What about all the things the experts don’t know but you can discover from data? And when data is not available, the cost of knowledge engineering seldom exceeds the benefit. Imagine if farmers had to engineer each cornstalk in turn, instead of sowing the seeds and letting them grow: we would all starve.

Perhaps more worrisome, while government policies should be intended to serve the many for the long term, they are being gamed by interested parties to ensure that they serve the few in the short term, with damaging impact over the long term. The Persona Project respondents could feel this. To them, they were outsiders and others were playing the game to their own advantage, and to the respondents’ disadvantage. These outcomes are systemic, and without a fundamental shift in how we manage the economy, they will get only more out of alignment with our hopes and assumptions. I believe that this shift needs to start with abandoning the perfectible-machine model of the economy. We should instead understand the economy in more natural terms, as a complex adaptive system—one that is too complex to be perfectible, one that continuously adapts in ways that will almost certainly frustrate any attempts to engineer it for perfection. In addition, rather than striving singularly for ever more efficiency, we need to strive for balance between efficiency and a second feature: resilience.

When you come down to it, alignment is about helping people understand what you want them to do. Most contributors will be motivated to ladder up to the top-line OKRs—assuming they know where to set the ladder. As our team got larger and more layered, we confronted new issues. One product manager was working on Premium, the enhanced subscription version of our app. Another focused on our API platform, to enable third parties like Fitbit to connect to MyFitnessPal and write data to it or applications on top of it. The third addressed our core login experience. All three had individual OKRs for what they hoped to accomplish—so far, so good. The problem was our shared engineering team, which got caught in the middle. The engineers weren’t aligned with the product managers’ objectives. They had their own infrastructure OKRs, to keep the plumbing going and the lights on. We assumed they could do it all—a big mistake. They got confused about what they should be working on, which could change without notice. (Sometimes it boiled down to which product manager yelled loudest.) As the engineers switched between projects from week to week, their efficiency dragged.

Web Application Development In this modern world of computer technology all people are using internet. In particular, to take advantage of this scenario the web provides a way for marketers to get to know the people visiting their sites and start communicating with them. One way of doing this is asking web visitors to subscribe to newsletters, to submit an application form when requesting information on products or provide details to customize their browsing experience when next visiting a particular website. In computing, a web application is a client–server software application in which the client runs in a web browser. HTML5 introduced explicit language support for making applications that are loaded as web pages, but can store data locally and continue to function while offline. Web Applications are dynamic web sites combined with server side programming which provide functionalities such as interacting with users, connecting to back-end databases, and generating results to browsers. Examples of Web Applications are Online Banking, Social Networking, Online Reservations, eCommerce / Shopping Cart Applications, Interactive Games, Online Training, Online Polls, Blogs, Online Forums, Content Management Systems, etc.. Applications are usually broken into logical chunks called “tiers”, where every tier is assigned a role. Traditional applications consist only of 1 tier, which resides on the client machine, but web applications lend themselves to an n-tiered approach by nature. Though many variations are possible, the most common structure is the three-tiered application. In its most common form, the three tiers are called presentation, application and storage, in this order. A web browser is the first tier (presentation), an engine using some dynamic Web content technology (such as ASP, CGI, ColdFusion, Dart, JSP/Java, Node.js, PHP, Python or Ruby on Rails) is the middle tier (application logic), and a database is the third tier (storage).The web browser sends requests to the middle tier, which services them by making queries and updates against the database and generates a user interface. Client Side Scripting / Coding – Client Side Scripting is the type of code that is executed or interpreted by browsers. Client Side Scripting is generally viewable by any visitor to a site (from the view menu click on “View Source” to view the source code). Below are some common Client Side Scripting technologies: HTML (HyperTextMarkup Language) CSS (Cascading Style Sheets) JavaScript Ajax (Asynchronous JavaScript and XML) jQuery (JavaScript Framework Library – commonly used in Ajax development) MooTools (JavaScript Framework Library – commonly used in Ajax development) Dojo Toolkit (JavaScript Framework Library – commonly used in Ajax development) Server Side Scripting / Coding – Server Side Scripting is the type of code that is executed or interpreted by the web server. Server Side Scripting is not viewable or accessible by any visitor or general public. Below are the common Server Side Scripting technologies: PHP (very common Server Side Scripting language – Linux / Unix based Open Source – free redistribution, usually combines with MySQL database) Zend Framework (PHP’s Object Oriented Web Application Framework) ASP (Microsoft Web Server (IIS) Scripting language) ASP.NET (Microsoft’s Web Application Framework – successor of ASP) ColdFusion (Adobe’s Web Application Framework) Ruby on Rails (Ruby programming’s Web Application Framework – free redistribution) Perl (general purpose high-level programming language and Server Side Scripting Language – free redistribution – lost its popularity to PHP) Python (general purpose high-level programming language and Server Side Scripting language – free redistribution). We also provide Training in various Computer Languages. TRIRID provide quality Web Application Development Services. Call us @ 8980010210

Building Information Modeling (BIM) is a trending 3D model-based process that gives architecture, engineering, and construction (AEC) professionals the insight and tools to more efficiently plan, design, construct and manage buildings and infrastructure. Arcengine provides the outsource bim services for AEC professionals to better understand the plan insights. We have professional bim staff having more than 6 years of experience in the real estate sector. Our primary focus is to make design error & revision free to decrease the turnaround time. We please to hear you from about your project. If you want to know more about us & the latest updates visit our website.

On another project the best engineering manager I ever saw served often as a giant flywheel, his inertia damping the fluctuations that came from market and management people.

As an engineer, you have a depth of knowledge about your systems and projects that no managers can possibly have. With that knowledge comes the responsibility to act.

An early lesson I learned in my career was that whenever a large organization attempts to do anything, it always comes down to a single person who can delay the entire project. An engineer might get stuck waiting for a decision or a manager may think she doesn’t have authority to make a critical purchase. These small, seemingly minor hesitations can cause fatal delays. I could not afford any hesitation, so I scheduled a daily meeting with Anthony, Jason, and the team

Good product managers don’t get all of their time sucked up by the various organizations that must work together to deliver the right product at the right time. They don’t take all the product team minutes; they don’t project manage the various functions; they are not gofers for engineering. They are not part of the product team; they manage the product team. Engineering teams don’t consider good product managers a “marketing resource.” Good product managers are the marketing counterparts to the engineering manager.

A project manager is the captain of the ship, the person responsible for making sure the project is on course and moving ahead smoothly. He or she is in charge of the schedule, and the allocation of money. But most of all, the project manager is responsible for maintaining relationships with the people providing the funds.

the part about the product manager not showing up for the demo pisses her off. What a disrespectful thing to do to engineers who built what you asked them to.

Leading the field in environmental expertise. Adeptus provides environmental consultancy, reporting and project management services. Our multidisciplinary team of environmental consultants and engineers is equipped to advise on projects of any type. Many of our clients operate within the sectors shown below, where we strive to find the most cost effective way to meet their objectives. Our core business is the assessment of land condition and the management of contaminated soil and waters.

As an engineer and later as a manager, I was accustomed to measuring progress by making sure our work proceeded according to plan, was high quality, and cost about what we had projected.

We have a very vast array of hands on computer technical support experience spanning twenty years as licensed Microsoft, Cisco and Novell computer network engineers. Computer Repair, Computer Service, Computer Support, Computer Consultant, Tech Support, IT Service, IT Support, PC Repair, Network Repair, Laptop Repair, Data Recovery, Disaster Recovery, Data Transfer, IT Repair, IT Consultant, PC Service, PC Support, PC Consultant, Network Service, Network Support, Network Consultant, Laptop Service, Laptop Support, IT Management, Computer Virus Removal, Computer Spyware Removal, Computer Services, Network and Wireless Installation, Server and Workstation Installation, Repair, Programming, IT Recruitment and Placement, Website Design, Website Promotion, Database Design, E-Commerce, Network Design, Network Audits, Internet Research and Sourcing, Computer Science Expert Witness, Computer Science Forensics, Disaster Recovery and Planning, Computer Consulting, Project Management, IT Department Outsourcing and Management, Maintenance Contracts, IT Audits, Free Onsite Needs Assessment, Search Engine Marketing, Search Engine Optimization, Computer Server Repair, Computer Network Repair.

Creative people are easily bored, moody, a bit difficult to handle. You have to make it fun for them, care for them. Creative people only produce really good work if you creatively challenge them. They have to like what they’re working on. They have to be damn proud of the fact that they’re a part of a particular project. That is again the task of the manager. Each time, you have to give them creative challenges. That’s difficult, but nobody said it is easy to lead creative people.

Social context and NOT individual abilities drives performance, success or failure of a team or a project.

Social context and NOT individual abilities drives performance, success or failure of a team or a project.

Where a typical manager may set the deadline for the employee, Musk guides his engineers into taking ownership of their own delivery dates. “He doesn’t say, ‘You have to do this by Friday at two P.M.,’” Brogan said. “He says, ‘I need the impossible done by Friday at two P.M. Can you do it?’ Then, when you say yes, you are not working hard because he told you to. You’re working hard for yourself. It’s a distinction you can feel. You have signed up to do your own work.” And by recruiting hundreds of bright, self-motivated people, SpaceX has maximized the power of the individual. One person putting in a sixteen-hour day ends up being much more effective than two people working eight-hour days together. The individual doesn’t have to hold meetings, reach a consensus, or bring other people up to speed on a project. He just keeps working and working and working. The

And to say that the citizens of those rival domains did not always see eye to eye was a bit of an understatement, because each represented the antithesis of the other’s deepest values. To the engineers and the technicians who belonged to the world of the dam, Glen was no dead monolith but, rather, a living and breathing thing, a creature that pulsed with energy and dynamism. Perhaps even more important, the dam was also a triumphant capstone of human ingenuity, the culmination of a civil-engineering lineage that had seen its first florescence in the irrigation canals of ancient Mesopotamia and China, then shot like a bold arrow through the Middle Ages, the Renaissance, and the Industrial Revolution to reach its zenith here in the sun-scorched wastelands of the American Southwest. Glen embodied the glittering inspiration and the tenacious drive of the American century—a spirit that in other contexts had been responsible for harnessing the atom and putting men on the moon. As impressive as those other accomplishments may have been, nothing excelled the nobility of transforming one of the harshest deserts on earth into a vibrant garden. In the minds of its engineers and its managers, Glen affirmed everything that was right about America. To Kenton Grua and the river folk who inhabited the world of the canyon, however, the dam was an offense against nature. Thanks to Glen and a host of similar Reclamation projects along the Colorado, one of the greatest rivers in the West, had been reduced to little more than a giant plumbing system, a network of pipes and faucets and catchment tubs whose chief purpose lay in the dubious goal of bringing golf courses to Phoenix, swimming pools to Tucson, and air-conditioned shopping malls to Vegas. A magnificent waterway had been sacrificed on the altar of a technology that enabled people to prosper without limits, without balance, without any connection to the environment in which they lived—and in the process, fostered the delusion that the desert had been conquered. But in the eyes of the river folk, even that wasn’t the real cost. To

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.

I believe that large programming projects suffer management problems different in kind from small ones, due to division of labor. I believe the critical need to be the preservation of the conceptual integrity of the product itself.

it sprang from a conviction that the quality of the people on a project, and their organization and management, are much more important factors in success than are the tools they use or the technical approaches they take. Subsequent researches have supported that conviction. Boehm's COCOMO model finds that the quality of the team is by far the largest factor in its success, indeed four times more potent than the next largest factor.

The job done least well by project managers is to utilize the technical genius who is not strong on management talent.

This is my self-assessment that I wrote in my performance review that year: Overall, my performance was dreadful in 2006. In Unbox, our launch was poorly received, partly due to DRM [digital rights management] and licensing issues that restrict content usage, and selection, partly due to bad product choices we made for consumers (erring on the side of quality over download speed) and partly due to engineering defects. In any case, I didn’t manage these issues appropriately and the result was a weak launch with weak consumer response and negative press reaction. Net my performance versus goals can be summarized by a poor execution percentage in terms of projects completed and the main project that is complete (Unbox Video) is not a compelling customer experience (yet) and the rate of sales is pitiful. I think a grade of ‘D’ for my performance vs. goals would be generous.

However, tech leads will be working on one major new technical skill: project management. The work of breaking down a project has a lot of similarity to the work of designing systems, and learning this skill is valuable even for engineers who don’t want to manage people.

If you are an engineer or an engineering manager, and take away only one thought from reading this book, here’s what I suggest it should be: “One hour projects take one hour to complete. Four hour projects take a day. One day projects take a week. One week projects take a couple of months. And, six month or longer projects tend to never complete.” Ken Williams

Just remember that a mix is good. Decider Who makes decisions for your team? Perhaps it’s the CEO, or maybe it’s just the “CEO” of this particular project. If she can’t join for the whole time, make sure she makes a couple of appearances and delegates a Decider (or two) who can be in the room at all times. Examples: CEO, founder, product manager, head of design Finance expert Who can explain where the money comes from (and where it goes)? Examples: CEO, CFO, business development manager Marketing expert Who crafts your company’s messages? Examples: CMO, marketer, PR, community manager Customer expert Who regularly talks to your customers one-on-one? Examples: researcher, sales, customer support Tech/logistics expert Who best understands what your company can build and deliver? Examples: CTO, engineer Design expert Who designs the products your company makes? Examples: designer, product manager

One key application of this maxim arises when we choose a collaborator, for example in an intellectual project or in business. As Richard frequently argues, we often choose people whose skills are similar to our own. The result is that the gains from collaboration are much smaller than if we were to choose people who would bring different capabilities to the undertaking. If two engineers are planning the construction of a bridge, adding a third engineer to the team won’t help as much as adding an architect or a project manager.

Law Firm & Construction Lawyer in Brisbane. Engineers with law degrees make the best construction lawyer. Wouldn't you want to talk about your project's construction-legal-commercial issues with someone who really understands them in Brisbane? An Engineer, Project Manager, QS and Planner who studied law and is now a Registered Solicitor and Adjudicator under the SOP Act in Queensland?, someone who spent 20 years with Leighton Contractors (now CIMIC/ CPB) and has over 30 years of first-hand experience in the development of many of Australia's iconic projects.

After comparing desired with available resources, it became crystal clear that the company was pursuing many more projects than it had people to staff. In particular, by trying to engage in many highly demanding platform launches at the same time, the company was unlikely to do justice to its portfolio of options. Nor was it likely to manage the enhancement launches (as opposed to platform launches) that current customers were demanding, because many of these were still on the drawing board and were competing for the same scarce design and engineering talent as the major platform launches. In short, the company was taking on too much. The results of this overcommitment meant that project deadlines perpetually slipped, promises to key customers were often broken, and people were beginning to feel burned out. This situation is not uncommon. The processes through which companies take on projects usually lead them to discover that they haven’t got the resources to do justice to everything on their plates. In particular, when managers have not clearly thought through which resources for projects will be needed to support their needs to either build new platforms or learn through options, the different types of projects compete with each other, creating confusion. This lack of coordination is also typical of companies that haven’t matched their strategy to available resources. A far wiser approach is to pursue a few well-run projects than to chase down a grab-bag of forever-behind-schedule and over-budget initiatives.

The main purpose of the Security Of Payments SOP Act is to help contractors working in the building and construction industry in being paid for the work they do. Wouldn't you want to talk about your project's construction-legal-commercial issues with someone who really understands them?, someone who has MEP and F trade qualifications and acted as Design Engineer, Engineering Manager, Project Manager, QS, Planner, studied law and is now a Registered Solicitor and Adjudicator under the SOP Act in Queensland?

Christy Lodwick, the Vice President of Tyde Systems, brings reliable skills and knowledge to the organization. Having served in the Health Care industry as an Administrator and Consultant, Christy Lodwick has the experience required to manage high-end projects at the company. Many clients benefit from her project managerial and network engineering skills.

The Wolf. The single most productive engineer you’ll meet. You’ve heard of the 10x engineer, but I am here to tell you about the Wolf. They are engineers, and they consistently exhibit the following characteristics: They appear to exist outside of the well-defined process that we’ve defined to get things done, but they appear to suffer no consequences for not following these rules. Everyone knows they’re the Wolf, but no one ever calls them the Wolf. They have a manager, but no one really knows who it is. They have a lot of meetings, but none of them are scheduled. Inviting them to your meeting is a crap shoot. They understand how “the system” works, they understand how to use “the system” to their advantage, and they understand why “the system” exists, but they think “the system” is a bit of a joke. You can ask a Wolf to become a manager, but they’ll resist it. If you happen to convince them to do it, they will do a fine job, but they won’t stay in that role long. In fact, they’ll likely quit managing when you least expect it. Lastly, and most importantly, the Wolf generates disproportionate value for the company with their unparalleled ability to identify and rapidly work on projects essential to the future of the company.

The sound that surrounds a successful regimen of one-on-ones is silence. All of the listening, questioning, and discussion that happens during a one-on-one is managerial preventative maintenance. You’ll see when interest in a project begins to wane and take action before it becomes job dissatisfaction. You’ll hear about tension between two employees and moderate a discussion before it becomes a yelling match in a meeting. Your reward for a culture of healthy one-on-ones is a distinct lack of drama.

Firstelite Certified engineering consultant office in S.A, all differente engineering works, from architectural designs, structural designs, engineering design, project implementation and management and engineering consultancy

A boat without a captain is nothing more than a floating waiting room: unless someone grabs the rudder and starts the engine, it’s just going to drift along aimlessly with the current. A piece of software is just like that boat: if no one pilots it, you’re left with a group of engineers burning up valuable time, just sitting around waiting for something to happen (or worse, still writing code that you don’t need).

Projects fail all the time, people screw up all the time. Usually it’s by failing to acknowledge missteps that we exacerbate them.

Indeed, that’s the only viable long-term bet on your career: focus on work that matters, do projects that develop you, and steer towards companies that value genuine experience.

Cosgrove advocates treating all plans, milestones, and schedules as tentative, so as to facilitate change. This goes much too far—the common failing of programming groups today is too little management control, not too much. Nevertheless, he offers a great insight. He observes that the reluctance to document designs is not due merely to laziness or time pressure. Instead it comes from the designer's reluctance to commit himself to the defense of decisions which he knows to be tentative. "By documenting a design, the designer exposes himself to the criticisms of everyone, and he must be able to defend everything he writes. If the organizational structure is threatening in any way, nothing is going to be documented until it is completely defensible." Structuring an organization for change is much harder than designing a system for change. Each man must be assigned to jobs that broaden him, so that the whole force is technically flexible. On a large project the manager needs to keep two or three top programmers as a technical cavalry that can gallop to the rescue wherever the battle is thickest. Management structures also need to be changed as the system changes. This means that the boss must give a great deal of attention to keeping his managers and his technical people as interchangeable as their talents allow.

Pitch example 2 Hi (journalist name), I would like to offer the news of a joint venture for your business pages.  Two industry leaders in the world of branding and signage from the UK and US have joined forces to form (the name of the joint venture), a one-stop design, engineering, manufacturing and project management solution for businesses across the globe. Do let me know if you need more information on this.  Regards (Name) Dissecting the pitch This pitch is about a branding joint venture and it’s a real pitch that I sent to a journalist for my client, which resulted in great coverage. Let’s break it down: Straight away, you know it’s a joint venture story.  I’ve been helpful enough to tell the journalist where it would fit, i.e. their business pages.  The credibility is enforced by saying two industry leaders in the world of branding and signage.  I’ve detailed the sector. I’ve mentioned the international collaboration by saying it’s a UK and US company. I briefly explain what they’re offering by saying it’s a one-stop design, engineering, manufacturing and project management solution. It’s a bit of a mouthful but the reason there was this much detail as opposed to the more straightforward doggy daycare, is because the audiences were very different. This is for the branding press and the business press, whereas the doggy daycare was aimed at the local media, who cover a range of topics.

Something that is somewhat ignored a bit here is how to handle urgent project requests when you’re already underwater with your existing work and maintenance. The most valuable skill in this situation is learning to say no in a way that is appropriate to your company’s culture.

Services Provided by TRIRID Welcome to TRIRID. Services Provided By TRIRID Mobile Application Development Web Application Development Custom Software Development Database Management Wordpress / PHP Search Engine Optimization Mobile Application Development We offer various Mobile Application Development services for most major platforms like Android, iPhone, .Net etc. At Tririd we develop customized applications considering the industry standards which meet all the customers requirements. Web Application Development Web Application Development technologies include PHP, Ajax, .Net, WordPress, HTML, JavaScript, Bootstrap, Joomla, etc. PHP language is considered one of the most popular & most widely accepted open source web development technology. PHP development is gaining ground in the technology market. Web development using these technologies is considered to offer the most efficient website solutions. The open source based products and tools are regularly studied, used, implemented and deployed by TRIRID. Custom Software Development TRIRID has incredible mastery in Windows Apps Development platform working on the .NET framework. We have done bunch of work for some companies and helping them to migrate to a new generation windows based solution. We at TRIRID absolutely comprehend your custom needs necessities and work in giving high caliber and adaptable web API services for your web presence. TRIRID offers a range of utility software packages to meet and assortment of correspondence needs while including peripherals. We offer development for utility software like plugin play, temperature controller observation or embedding solutions. Database Management In any organization data is the main foundation of information, knowledge and ultimately the wisdom for correct decisions and actions. On the off chance that the data is important, finished, exact, auspicious, steady, significant and usable, at that point it will doubtlessly help in the development of the organization If not, it can turn out to be a useless and even harmful resource. Our team of database experts analyse your database and find out what causes the performance issues and then either suggest or settle the arrangement ourselves. We provide optimization for fast processing better memory management and data security. Wordpress / PHP WordPress, based on MySQL and PHP, is an open source content management system and blogging tool. TRIRID have years of experience in offering different Web design and Web development solutions to our clients and we specialize in WordPress website development. Our capable team of WordPress designers offers all the essential services backed by the stat-of-the-art technology tools. PHP is perhaps the most effective and powerful programming language used to create dynamic sites and applications. TRIRID has extensive knowledge and experience of giving web developing services using this popular programming language. Search Engine Optimization SEO stands for search engine optimization. Search engine optimization is a methodology of strategies, techniques and tactics used to increase the amount of visitors to a website by obtaining a high-ranking placement in the search results page of a search engine (SERP) — including Google, Bing, Yahoo and other search engines. Call now 8980010210

There are only three of these activities that the Systems Integrator MUST provide and MUST be expert at. These are: Project Management, Systems Engineering, and Subcontract Management. Everything else can be assigned to subcontractors to perform, but these three activities must be performed by the prime contractor.

Exploration is hard to justify because it’s hard to measure. When exploration is complete, you often have nothing to hold up to your project manager to explain or justify the expenditure of time. Here’s what you tell them: “My job isn’t just building product; I also build people.

Project managers, designers, and engineers in the built industry are fortunate to see the product of their work every day in schools, office buildings, industrial parks, streets, and bridges. But too often, they lose the why behind their work in the busyness of doing the work. They lose the connection and meaning to their work.

Building a product is like making a song. The band is composed of marketing, sales, engineering, support, manufacturing, PR, legal. And the product manager is the producer—making sure everyone knows the melody, that nobody is out of tune and everyone is doing their part. They’re the only person who can see and hear how all the pieces are coming together, so they can tell when there’s too much bassoon or when a drum solo’s going on too long, when features get out of whack or people get so caught up in their own project that they forget the big picture.

An early lesson I learned in my career was that whenever a large organization attempts to do anything, it always comes down to a single person who can delay the entire project. An engineer might get stuck waiting for a decision or a manager may think she doesn’t have authority to make a critical purchase. These small, seemingly minor hesitations can cause fatal delays. I could not afford any hesitation, so I scheduled a daily meeting with Anthony, Jason, and the team—though they were now based in Plano. The purpose was to remove all roadblocks.

Product managers look for places where the customer is unhappy. They unravel issues as they go, discovering the root of the problem and working with the team to solve it. They do whatever is necessary to move projects forward—that could be taking notes in meetings or triaging bugs or summarizing customer feedback or organizing team docs or sitting down with designers and sketching something out or meeting with engineering and digging into the code. It’s different for every product.

Software Engineering Institute Technical Report (SEI

The success of project greatly dependent on periodic visualization of outcome.

Though time management seems a problem as old as time itself, the science of scheduling began in the machine shops of the industrial revolution. In 1874, Frederick Taylor, the son of a wealthy lawyer, turned down his acceptance at Harvard to become an apprentice machinist at Enterprise Hydraulic Works in Philadelphia. Four years later, he completed his apprenticeship and began working at the Midvale Steel Works, where he rose through the ranks from lathe operator to machine shop foreman and ultimately to chief engineer. In the process, he came to believe that the time of the machines (and people) he oversaw was not being used very well, leading him to develop a discipline he called “Scientific Management.” Taylor created a planning office, at the heart of which was a bulletin board displaying the shop’s schedule for all to see. The board depicted every machine in the shop, showing the task currently being carried out by that machine and all the tasks waiting for it. This practice would be built upon by Taylor’s colleague Henry Gantt, who in the 1910s developed the Gantt charts that would help organize many of the twentieth century’s most ambitious construction projects, from the Hoover Dam to the Interstate Highway System. A century later, Gantt charts still adorn the walls and screens of project managers at firms like Amazon, IKEA, and SpaceX.

Capitalism began as a theory about how the economy functions. It was both descriptive and prescriptive – it offered an account of how money worked and promoted the idea that reinvesting profits in production leads to fast economic growth. But capitalism gradually became far more than just an economic doctrine. It now encompasses an ethic – a set of teachings about how people should behave, educate their children and even think. Its principal tenet is that economic growth is the supreme good, or at least a proxy for the supreme good, because justice, freedom and even happiness all depend on economic growth. Ask a capitalist how to bring justice and political freedom to a place like Zimbabwe or Afghanistan, and you are likely to get a lecture on how economic affluence and a thriving middle class are essential for stable democratic institutions, and about the need therefore to inculcate Afghan tribesmen in the values of free enterprise, thrift and self-reliance. This new religion has had a decisive influence on the development of modern science, too. Scientific research is usually funded by either governments or private businesses. When capitalist governments and businesses consider investing in a particular scientific project, the first questions are usually ‘Will this project enable us to increase production and profits? Will it produce economic growth?’ A project that can’t clear these hurdles has little chance of finding a sponsor. No history of modern science can leave capitalism out of the picture. Conversely, the history of capitalism is unintelligible without taking science into account. Capitalism’s belief in perpetual economic growth flies in the face of almost everything we know about the universe. A society of wolves would be extremely foolish to believe that the supply of sheep would keep on growing indefinitely. The human economy has nevertheless managed to keep on growing throughout the modern era, thanks only to the fact that scientists come up with another discovery or gadget every few years – such as the continent of America, the internal combustion engine, or genetically engineered sheep. Banks and governments print money, but ultimately, it is the scientists who foot the bill. Over the last few years, banks and governments have been frenziedly printing money. Everybody is terrified that the current economic crisis may stop the growth of the economy. So they are creating trillions of dollars, euros and yen out of thin air, pumping cheap credit into the system, and hoping that the scientists, technicians and engineers will manage to come up with something really big, before the bubble bursts. Everything depends on the people in the labs. New discoveries in fields such as biotechnology and nanotechnology could create entire new industries, whose profits could back the trillions of make-believe money that the banks and governments have created since 2008. If the labs do not fulfil these expectations before the bubble bursts, we are heading towards very rough times.

Action Steps 1. Audit your current skill set. You have more areas of competence than you think. Throughout your life, you have amassed knowledge and specialized skills in a wide range of disciplines. That knowledge and those skills can prove useful to you in future endeavors. For example, I have a degree in Finance and Investments. Upon graduating from college, I accepted an accounting position with one of the top automakers. I then became a stockbroker. Then, I moved into a career in IT. For the past 20 years, I’ve been a writer in numerous capacities. Along the way, I learned about server management, Wordpress development and search engine optimization. All of these ventures imbued me with skills I use every day - in my business and personal life. Your experience has likewise instilled within you a raft of specialized skills. Many of them will help you to tackle unfamiliar tasks and projects, even if they seem unrelated to your current and previous jobs. 2. Focus on your desired outcomes rather than the things that might go wrong along the way. One of our survival instincts is to plan for things that might go wrong. In some circumstances, that’s a valuable quality that protects us from harm. It prevents us from strolling down dark alleys in unpopulated locales. It discourages us from petting strange dogs. In other circumstances, however, it can hold us back. The instinct prevents us from pursuing opportunities that can lead to improved aptitude as well as personal and professional growth. By focusing on your desire outcomes, you’ll find it easier to ignore your inborn fear of the unknown. You’ll be able to dismiss the voice in your head constantly whispering “What if XYZ happens?” 3. Look for opportunities to learn new skills. The self-confidence you’ll gain will make you less fearful of tackling unfamiliar tasks. Achieving a high level of competency in any discipline requires repeated exposure and application. There’s no other way to attain proficiency. The problem is a lack of courage. It’s normal to feel hesitant, or even intimidated, when we’re given a new responsibility.

There are people who talk about operating experience and there are people who say it’s about risk-taking or process, or due diligence, but it’s about none of that. People have gut feelings about things and there are lots of ways that they rationalize themselves into their investment decisions. Very few people are willing to take the risk and fund some of these things that turn out to be crazy large, whether it’s Amazon (which was a book store), Google (which was the 27th search engine), or Genentech (which really was just a science project). None of those things in 20/20 hindsight were rational decisions you would make. It takes risk-takers to do seed investing, not risk managers.

Decider Who makes decisions for your team? Perhaps it’s the CEO, or maybe it’s just the “CEO” of this particular project. If she can’t join for the whole time, make sure she makes a couple of appearances and delegates a Decider (or two) who can be in the room at all times. Examples: CEO, founder, product manager, head of design Finance expert Who can explain where the money comes from (and where it goes)? Examples: CEO, CFO, business development manager Marketing expert Who crafts your company’s messages? Examples: CMO, marketer, PR, community manager Customer expert Who regularly talks to your customers one-on-one? Examples: researcher, sales, customer support Tech/logistics expert Who best understands what your company can build and deliver? Examples: CTO, engineer Design expert Who designs the products your company makes? Examples: designer, product manager

Unless your problem is that people aren’t trying hard, the “work harder” mantra only breeds hero programmers whose heroic ways make it difficult for nonheroes to contribute meaningfully. Later, as your new heroes finish martyring themselves on burnout, you’re left with three exceptionally challenging problems: You’ve bred a cadre of dissatisfied and burned-out heroes. You and your heroes have alienated everyone else. Your project is still totally screwed. This is a recurring pattern that many growing companies fall into, and it also happens to projects within larger companies. Anywhere you find managerial desperation and a hardworking team, “Do It Harder” may be visiting.

One of the observations from systems thinking16 is that, though humans are prone to interpreting events as causal, often problems are better described in terms of a series of stockpiles that grow and shrink based on incoming and outgoing flows. The Dust Bowl17 wasn’t caused by one farmer or one year of overfarming, but by years of systemic abuse. Stocks and flows are especially valuable in understanding the failure of projects and teams. Projects fall behind one sprint at a time. Technical debt strangles projects over months. Projects fail slowly—and fixing them takes time, too.