DEV Community: Petr Dme

affiliate marketing

Petr Dme — Sun, 12 Jan 2025 12:40:11 +0000

3 Github Repositories That Will Help To Side Hustle

Petr Dme — Sat, 24 Feb 2024 22:51:02 +0000

So, I'm a software engineer who is trying to look for extra income in many ways. I do freelance, digital marketing, and also affiliate marketing. Although the income from these side hustles is not as great as my main job as a software engineer, I believe that making extra income as a side hustler will help my finances.

Along with my effort, I collected some repositories that can help me to do my side hustle. One of them is my repository, but I believe it will help you with side hustling.

GitHub is a treasure trove of repositories that can make your side projects more efficient and enjoyable. Here are three GitHub repositories that can give your side hustle the edge it needs:

awesome-seo:
Link: awesome-seo
Description:
The author, madawei2699, is a Chinese developer. He has been organizing a checklist since a systematic study of Google SEO in 2019. The checklist undergoes periodic updates. Additionally, contributions in the form of PRs are welcome to his repo, along with the sharing of valuable links related to SEO.
This repository contains guides and also curated list of tools related to SEO.
At the time of this article, the repository got more than 2K stars.
Software Engineer Affiliate Program Hub:
Link: software-engineer-affiliate-program-hub
Description: This is my repo. It is still growing, but I believe it will help any software engineer to learn about affiliate marketing. It contains a curated list of affiliate programs that are relatable to software engineers. For example, some tools that provide API also has an affiliate program. A software engineer can promote this kind of tool as they can also use it themselves for their work.
Along with that, it also contains several guides on many things related to digital marketing.
Awesome Digital Marketing
Link: awesome-digital-marketing
Description: 😎 A curated list of awesome digital marketing guides, resources, services, & more. That is the description made by the author, Paul Bradish. It contains a wide range of tools that can help people in digital marketing. It is intended for both software engineers and also digital marketers.

These repositories cover a spectrum of side hustle interests, from SEO to specific technology implementations and learning paths. Remember, the key to a successful side hustle is consistent effort and continuous learning. Happy side hustling!

Summary: Turning Tech Hobbies into Side Hustle by Erik Dietrich

Petr Dme — Tue, 02 Jan 2024 22:50:34 +0000

Recently, I read this article from @daedtech, and somehow I'm interested. So, I want to summarize in points that I can remember easily. Think of it as a journal.

Introduction with a Tweet: Erik shares a tweet from six years ago about wanting to learn F# and explains how this tweet sets the stage for discussing the distinction between technical hobbies and side hustles.
Technical Hobbies vs. Career: Erik explores the difference between technical hobbies (like learning programming languages) and activities that contribute to your career.
Motivations Behind Learning: It dives into the multiple motivations that drive individuals to pursue additional programming skills and knowledge, including personal interests, challenges, and self-improvement.
Impressing Peers vs. Buyers: Erik discusses the tendency in the programming world to focus on impressing peers rather than attracting potential clients or employers.
Status vs. Opportunity: Erik illustrates how having technical celebrity status doesn't necessarily translate into substantial opportunities unless you can establish your audience as potential buyers.
K. Scott Allen's Success: Erik highlights the success of K. Scott Allen, who managed to turn his technical celebrity into substantial earnings by appealing not only to fellow programmers but also to buyers.
The Importance of a "Who and Do What" Statement: Erik emphasizes the importance of having a clear "who and do what" statement to explain your work, helping you align your learning efforts with potential side hustles.
Find a Buyer: It encourages readers to find a way to turn their learning into a side hustle that benefits someone else, ensuring that the newfound skill has a practical application.
Conclusion: The article concludes by advising readers to avoid learning for the sake of learning only and instead seek ways to make their learning efforts pay off through a side hustle that serves a specific audience or buyer.

Checklist: How to Create a GooD Article in Dev.To

Petr Dme — Thu, 28 Dec 2023 02:04:21 +0000

If you notice the capital "D" in "GooD", it is intentionally to attract the reader :p

I'm an organized person, so I always create a checklist before I do something big. Here, I make a checklist on how to create a good article in Dev.To. I hope this will help you.

[ ] Choose a Relevant Topic: Select a topic that is relevant to the Dev.to community and aligns with your expertise and interests.
[ ] Research and Plan: Conduct thorough research on your chosen topic and plan your post's structure and key points.
[ ] Catchy Title: Create an engaging and descriptive title that entices readers to click and read your post.
[ ] Clear Introduction: Write a clear and concise introduction that provides context and sets expectations for your readers.
[ ] Well-Structured Content: Organize your content into sections or headings, making it easy for readers to follow and understand.
[ ] Use Code Snippets: If applicable, include code snippets, examples, or demos to illustrate your points.
[ ] Visuals and Media: Incorporate relevant images, charts, or diagrams to enhance understanding and engagement.
[ ] Write Clear and Concise: Use clear and concise language, avoiding jargon or unnecessary complexity.
[ ] Proofread and Edit: Carefully proofread your post for grammar, spelling, and formatting errors. Edit for clarity and coherence.
[ ] Engage with the Community: Respond to comments and engage with readers who provide feedback or ask questions.
[ ] Cite Sources: If you reference external sources or research, provide proper citations and attribution.
[ ] Share Your Experience: Share personal anecdotes or experiences related to the topic, making your post more relatable.
[ ] Call to Action: Include a call to action (CTA) at the end of your post, encouraging readers to engage, share, or provide feedback.
[ ] Add Relevant Tags: Use relevant tags to categorize your post and make it easier for users to discover.
[ ] Preview and Publish: Review your post in the preview mode to ensure it looks and reads as intended, then hit the "Publish" button.
[ ] Promote Your Post: Share your post on social media and other relevant platforms to reach a wider audience.
[ ] Stay Engaged: Stay engaged with the Dev.to community by reading, commenting on, and supporting other posts.

P.S: Unfortunately, Dev.To is not converting checklist syntax markdown, so here is the checklist markdown in the code

- [ ] Choose a Relevant Topic: Select a topic that is relevant to the Dev.to community and aligns with your expertise and interests.

- [ ] Research and Plan: Conduct thorough research on your chosen topic and plan your post's structure and key points.

- [ ] Catchy Title: Create an engaging and descriptive title that entices readers to click and read your post.

- [ ] Clear Introduction: Write a clear and concise introduction that provides context and sets expectations for your readers.

- [ ] Well-Structured Content: Organize your content into sections or headings, making it easy for readers to follow and understand.

- [ ] Use Code Snippets: If applicable, include code snippets, examples, or demos to illustrate your points.

- [ ] Visuals and Media: Incorporate relevant images, charts, or diagrams to enhance understanding and engagement.

- [ ] Write Clear and Concise: Use clear and concise language, avoiding jargon or unnecessary complexity.

- [ ] Proofread and Edit: Carefully proofread your post for grammar, spelling, and formatting errors. Edit for clarity and coherence.

- [ ] Engage with the Community: Respond to comments and engage with readers who provide feedback or ask questions.

- [ ] Cite Sources: If you reference external sources or research, provide proper citations and attribution.

- [ ] Share Your Experience: Share personal anecdotes or experiences related to the topic, making your post more relatable.

- [ ] Call to Action: Include a call to action (CTA) at the end of your post, encouraging readers to engage, share, or provide feedback.

- [ ] Add Relevant Tags: Use relevant tags to categorize your post and make it easier for users to discover.

- [ ] Preview and Publish: Review your post in the preview mode to ensure it looks and reads as intended, then hit the "Publish" button.

- [ ] Promote Your Post: Share your post on social media and other relevant platforms to reach a wider audience.

- [ ] Stay Engaged: Stay engaged with the Dev.to community by reading, commenting on, and supporting other posts.

Tips for Writing Clean and Maintainable Code

Petr Dme — Tue, 19 Dec 2023 11:37:21 +0000

Hello, as a senior software developer, I often see junior devs not doing these obvious steps to write clean and maintainable code. this list is non-exhaustive.

Use Meaningful Names: Choose variable, method, and class names that clearly describe their purpose. Avoid ambiguous or generic names.
Follow a Consistent Coding Style: Adhere to a coding standard like PEP8 for Python or the Google Style Guides. This includes indentation, brackets, and naming conventions.
Write Small, Reusable Functions: Keep functions short and focused on a single task. This makes them easier to understand and reuse.
Comment and Document Wisely: Write meaningful comments that explain the 'why' behind complex logic, not the 'how'. Keep documentation up to date.
Refactor Regularly: Regularly revisit and refactor code to improve efficiency, readability, and maintainability.
Avoid Deep Nesting: Limit nesting of loops and conditionals. Deep nesting can make code hard to read and follow.
Implement Error Handling: Graceful error handling and clear error messages can make your code more robust and user-friendly.
Prioritize Code Reviews: Peer reviews can catch errors, ensure adherence to standards, and facilitate knowledge sharing.
Keep Learning and Updating: Stay updated with the latest best practices and continuously improve your coding skills.