Amateur Professional
🔞 ALL INFORMATION CLICK HERE 👈🏻👈🏻👈🏻
Amateur Professional
Mental Models
Decision Making
Reading Better
Best Articles
Random Article
Tags
Blog Self-Improvement The Difference Between Amateurs and Professionals
Farnam Street
Newsletter
Podcast
Learning Community
Books
Speaking
About
Categories
Mental Models
Learning
Reading
Decision Making
Intellectual Giants
Why is it that some people seem to be hugely successful and do so much, while the vast majority of us struggle to tread water?
The answer is complicated and likely multifaceted.
One aspect is mindset—specifically, the difference between amateurs and professionals.
What’s the difference? Actually, there are many differences:
There are a host of other differences, but they can effectively be boiled down to two things: fear and reality.
Amateurs believe that the world should work the way they want it to. Professionals realize that they have to work with the world as they find it . Amateurs are scared — scared to be vulnerable and honest with themselves. Professionals feel like they are capable of handling almost anything.
Luck aside, which approach do you think is going to yield better results?
Ideas in this article from Ryan Holiday, Ramit Sethi, Seth Godin and others.
Recently, shame has gotten a bad rap. It’s been branded as toxic and destructive. But shame can be used as a tool to effect positive change. *** A computer science PhD candidate uncovers significant privacy-violating security flaws in large companies, then shares them with the media to attract negative coverage. Google begins marking unencrypted websites […]
Performance reviews are designed to motivate and bring the best out of our teams, but they often do the opposite. Here’s how to bring out the best in your people. *** If you ask people what’s wrong with corporate workplaces, it won’t take long before you hear someone mention something about being put into a […]
We’re taught single loop learning from the time we are in grade school, but there’s a better way. Double loop learning is the quickest and most efficient way to learn anything that you want to “stick.” *** So, you’ve done the work necessary to have an opinion, learned the mental models, and considered how you […]
2021 Farnam Street Media Inc. All Rights Reserved.
Hosted by Pressable . See our Privacy Policy. Farnam Street participates in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising commissions by linking to Amazon.
We're Syrus Partners . We buy amazing businesses.
Amateur professionalism - Wikipedia
The Difference Between Amateurs and Professionals
The Difference Between a Professional and an Amateur
5 Differences Between Amateurs And Professionals (And How to Turn Pro )
What Makes The Difference Between Professionals and Amateurs ?
by Mike Cohn
90 Comments
Tagged:
teams
project management
An agile team should provide visibility into its work. But not all work should be equally transparent.
Aug 18, 2020
19 Comments
Apr 09, 2019
27 Comments
Oct 09, 2018
14 Comments
Jul 10, 2018
57 Comments
Feb 06, 2018
50 Comments
An agile team should provide visibility into its work. But not all work should be equally transparent.
Aug 18, 2020
19 Comments
Apr 09, 2019
27 Comments
Oct 09, 2018
14 Comments
Jul 10, 2018
57 Comments
Feb 06, 2018
50 Comments
Learn About Agile
New to Agile and Scrum?
Scrum
User Stories
Planning Poker
Agile Software Development
Agile Project Management
Agile & Scrum Training
Online Certifications
Video Courses
In-Person Certifications
On-Site Courses
Training Schedule
Compare Courses
PDUs and SEUs
More…
About Us
Contact Us
Blog
Books by Mike Cohn
Agile Tools
Copyright ©1998-2021 Mountain Goat Software. All Rights Reserved.
Contact Us
Terms and Conditions
Privacy Policy
Commenting Policy
Help
Are you a professional or an amateur?
I'm going to ask you to consider being a professional. But, before I do and before you can answer the question I posed, I need to make sure you are fully aware of what I mean when I talk about being a professional.
For me, the difference is simple: A professional always does everything necessary to complete a job. An amateur sometimes chooses only the fun parts.
An amateur golfer, for example, may thrill at the crack of hitting a 300-yard drive but hate putting. And so that amateur may frequently choose to pick up the ball once it's "close enough" to the hole.
A professional golfer could never do this. The professional may still prefer hitting the long drives over making intricate putts. But the professional knows he needs to do both parts of the job.
The difference between professionals and amateurs shows up on software teams in the team members who only do the portions of the job they like.
This can happen on any role on a project. It could be the tester who doesn't enjoy talking to customers ("Analysts do that."). Or it could be the product owner who only wants to think about strategic, big new features rather than going into the nitty gritty of the implementation.
For any job there are good parts and the bad parts. The professionals do the full job, not just the fun parts.
One of the more common amateurs I've been encountering lately are programmers who will only code exactly what they are told. "I gave you precisely what you asked for," they'll say. And there's nothing wrong with that reply in some cases. But it's not appropriate all the time.
The professional programmer brings his or her full brain, experience and creativity to the job. When asked to develop a feature, the professional thinks about it: Are there gaps in what was asked for? Are there alternative and better solutions? Will it lead to later problems? And then the professional has conversations with the product owner based on the answers to these questions to determine exactly what the feature will look like when implemented.
In contrast, the amateur says, "OK, I'll give you exactly what you asked for." That's easier. The amateur programmer doesn't have to think about the work beyond the specification. Just code what was asked for.
Similarly, an amateur programmer says, "I just write code; I don't test." Oh, that programmer will probably do a bit of testing on his or her own code. But when the team nears the end of a sprint and could use a little help testing for a day, an amateur programmer is likely to just code ahead on the next features rather than doing the more helpful--but to some, less desirable--work of helping test.
Not doing all parts of a job is a luxury only afforded to amateurs. An amateur can hit the glamourous, powerful 300-yard drive and then pick up the ball on the green without putting. The amateur can write code and not be concerned that no users are benefitting from that code until a tester catches up and tests it weeks later.
A professional knows that ultimately his job is to do whatever it takes to help the team. Often that means taking the time to have conversations about the tasks at hand or taking on some of the less desirable parts of the work.
It’s hard to be agile with a team composed largely of amateurs. Amateurs tend to take the distinctly non-agile attitude of “that isn’t my job” and “I only do this type of work.”
Amateurs are more likely to be highly specialized and to feel entitled to work solely within their one specialization. While this can lead to people in that role feeling more efficient, it will reduce the overall throughput of the team. (That is, overall team velocity will suffer even though one role may feel more efficient.)
For many reasons, a team of amateurs makes software development more difficult.
In the comments section below, please share your thoughts.
Are you an amateur or a professional? How do you stay motivated to always do the less glamorous parts of your job? How have you convinced amateurs to become professionals?
Get a free copy of Situational Scrum Mastering: Leading an Agile Team
Mike Cohn specializes in helping companies adopt and improve their use of agile processes and techniques to build extremely high-performance teams. He is the author of User Stories Applied for Agile Software Development, Agile Estimating and Planning, and Succeeding with Agile as well as the Better User Stories video course. Mike is a founding member of the Agile Alliance and Scrum Alliance and can be reached at hello@mountaingoatsoftware.com . If you want to succeed with agile, you can also have Mike email you a short tip each week.
Most individuals know that multitasking slows us down. It has an equally negative effect on agile …
Traditionally managed projects begin with a kickoff meeting. Here’s why and how agile projects can …
Are you struggling to find a catchy name for your agile team? Use this fun, mostly silly, generator …
We may think the Beatles simply sang about love, walruses and peace. But their songs actually …
Most individuals know that multitasking slows us down. It has an equally negative effect on agile …
Traditionally managed projects begin with a kickoff meeting. Here’s why and how agile projects can …
Are you struggling to find a catchy name for your agile team? Use this fun, mostly silly, generator …
We may think the Beatles simply sang about love, walruses and peace. But their songs actually …
Xxx Hikoyalar
Amateur France
Ngentot Xxx
Old Amateur Women
Girls Xxx
