Introduction
Hey, DEV world! 👋
Today's topic of discussion will be around a very intriguing subject:
— To be in motion or to act?
This topic came to my mind when I was looking for a project for Hacktoberfest 2021, when I was going through numerous projects with this hashtag on GitHub for the whole evening.
And then I closed my laptop with a feeling of satisfaction… but I still hadn't chosen a project or written a line of code!
Let's get started! 👇
📝 Table of contents
- What is the difference between movement and action?
- A life story to cover this principle
- Talk about it
What is the difference between movement and action?
You probably think that “being on the move” and “acting” are the same thing. Not exactly! Have you ever caught yourself thinking that it seems like a lot has been done, but there are no results?
— This is the “trap” because you've mistaken “motion” for “action”.
When we are in motion, we are strategizing, planning, or seeking knowledge. This can make it feel like we're moving forward, when in fact we're no closer to results at all.
Actions, on the other hand, bring concrete results. For example:
❌ To come up with 15 ideas for an article is to be in motion.
✅ To write a specific one article is already action.
❌ Watching numerous tutorial videos about programming is to be in motion.
✅ Developing a real application is already an action.
❌ Learning information about proper nutrition is to be in motion.
✅ Eating right is already an action.
It's critical to realize this frontier to become aware of many things in your work and even life, and to be more productive where you are now.
A life story to cover this principle
I like one of the stories I read in this Telegram channel (in Russian, sorry), where this same topic brought up (which is where I got my inspiration for this discussion).
It encapsulates perfectly the principle I've already announced earlier.
On the first day of film photography class, Jerry Uelsmann, a photographer and professor at the University of Florida, divided all the students into two groups. The goal of the first group was to work on quantity, the second on quality.
At the end of the semester, students in the first group will receive grades based on the number of pictures taken:
- One hundred pictures — 5 points;
- Ninety pictures — 4 points;
- …and so on;
Students in the second group will receive marks based on a subjective assessment of the quality of a single photo. By the end of the semester they only need to take one photo, but to get 5 points, it must be almost perfect.
— Which group do you think took the best pictures?
As it turns out, the highest quality pictures taken by the participants in the first group. By practicing a lot, such as lighting, composition, and testing different angles to get the right number of shots, they honed their skills and increased their chances of taking a classy picture.
The second group spent a lot of time thinking and searching for ideas for the perfect photo. They were constantly on the move, but not in action.
Talk about it
Being on the move is important! But if it doesn't lead to concrete action, it doesn't make any sense. Write what you think about this topic in the comments.
Let's discuss it together now! 💬
Photos and videos by
- Thought Catalog https://unsplash.com/photos/FACFpJVoMJs
- Alif Ngoylung https://unsplash.com/photos/jg-6ARMiaPM
P.S.
If you want more articles (like this) on this blog, then post a comment below and subscribe to me. Thanks! 😻
And of course, you can help me make developers' lives even better! Just connect to one of my projects as a contributor. It's easy!
My projects that need your help (and stars) 👇
- 🔥 gowebly: A next-generation CLI tool for easily build amazing web applications with Go on the backend, using htmx & hyperscript and the most popular atomic/utility-first CSS frameworks on the frontend.
- ✨ create-go-app: Create a new production-ready project with Go backend, frontend and deploy automation by running one CLI command.
- 🏃 yatr: Yet Another Task Runner allows you to organize and automate your routine operations that you normally do in Makefile (or else) for each project.
- 📚 gosl: The Go Snippet Library provides snippets collection for working with routine operations in your Go programs with a super user-friendly API and the most efficient performance.
- 🏄♂️ csv2api: The parser reads the CSV file with the raw data, filters the records, identifies fields to be changed, and sends a request to update the data to the specified endpoint of your REST API.
- 🚴 json2csv: The parser can read given folder with JSON files, filtering and qualifying input data with intent & stop words dictionaries and save results to CSV files by given chunk size.
Top comments (3)
@koddr sometimes we quality is very much required right!!
at beginning I believe we can compromise with quality on concentrate on quantity but as days passs, learning skills, One has to focus more on quality to become professional in the same field.
Like the
picture should speak louder than he speaksJust in time!
I'm in the "motion" mode for a long long while and now started to act a little. Very awkward feeling and a lot regrets "why didn't I do it before"
Hope to never fall in this trap again
You're welcome! :)