Forem: Dortey Tetteh

As a Techie: Balancing Growth with Boundaries

Dortey Tetteh — Thu, 12 Dec 2024 21:06:15 +0000

In the tech world, the pressure to stay updated with ever-changing tools and technologies can be overwhelming. Add this to daily responsibilities like debugging code, managing projects, or delivering on tight deadlines, and it’s easy to see why burnout is a constant threat. Here’s how boundaries can help:

Saying “No” to Scope Creep As a developer or project contributor, learn to push back when additional tasks are added to your plate without proper planning. Politely assert, “This seems important. Let’s discuss where it fits in the timeline or deprioritize something else.”
Boundaries in Learning It’s tempting to try and master every trending framework or language. However, focus on technologies aligned with your current or future goals. Block out specific times for skill-building. Whether that’s deep-diving into JavaScript, practicing Git workflows, or experimenting with real-world projects.

Tech-Specific Tip: Use tools like Focus Mode in VS Code or browser extensions to block distractions during your learning or work sessions.

In General: Guarding Your Time
Outside the tech bubble, boundary-setting is about saying “yes” to your priorities and “no” to distractions. Here’s how to effectively manage:

Family and Social Expectations Clearly communicate your goals with loved ones. Let them know why it’s important to have uninterrupted time, whether it’s for self-growth, learning, or work. Frame it as an investment in your future that benefits everyone.
Managing Workplace Overload In non-tech settings, overcommitment often stems from unclear roles or expectations. Clarify your priorities with your manager and be transparent about what you can realistically handle.
Personal Boundaries Setting boundaries with yourself is crucial. For instance, avoid binge-watching or endlessly scrolling social media when you’ve set aside time for learning. A little self-discipline here goes a long way.

Actionable Tip: Utilize tools like Google Calendar or Notion to plan your day and allocate time for specific tasks. Treat these time blocks as non-negotiable commitments.

Common Challenges and How to Overcome Them

Fear of Disappointing Others Saying “no” might feel selfish or rude, but it’s necessary. Practice polite but firm ways to decline, like, “I’d love to help, but I’m currently focused on XYZ.”
Unforeseen Interruptions Be flexible but firm. If someone disrupts your time, address it: “Can this wait until [insert time]? I’m currently in the middle of something important.”
Internal Guilt Remind yourself that rest and focus are critical to productivity. You’re not just working or learning, you’re preserving your mental health.

Takeaways
Setting boundaries is a superpower, whether you're building apps, analyzing data, or balancing career and family. Here’s the essence:

Be clear about your priorities.
Communicate your availability.
Stick to your schedule. Boundaries are not walls—they’re bridges to a healthier, more productive life.

Overcoming Your Fear and Starting Your First Coding Project

Dortey Tetteh — Mon, 25 Nov 2024 00:36:38 +0000

Starting your first coding project can be both exciting and nerve-wracking. Trust me, I’ve been there. Staring at a blank screen, wondering if I have what it takes to create something meaningful. The doubts can be loud: What if it’s not good enough? What if I fail? But here’s the truth: no one starts as an expert, and every great developer began with their very first project.

The most important step is to start. Let me share a few tips that helped me overcome my fears and get that first project off the ground.

Start Small, Dream Big Your first project doesn’t need to be a revolutionary app or the next viral website. It’s about getting comfortable, building confidence, and learning by doing. My first project was a simple personal portfolio page—a little corner of the internet to showcase my learning journey.

Here are a few beginner-friendly ideas:

A personal portfolio to track your progress.

A simple blog template with placeholder content.

A landing page for a pretend product, event, or service.

These bite-sized projects are perfect for practicing the basics without feeling overwhelmed. Remember, small steps lead to big milestones.

Find Inspiration in Templates If you’re struggling to come up with ideas or don’t know where to begin, use templates for inspiration. Platforms like Dribbble and Behance are treasure troves of simple, creative designs.

Pick a design you like and challenge yourself to recreate it using HTML and CSS. When I did this for the first time, it taught me so much about layout and styling, and gave me a sense of accomplishment when I saw my version come to life!

Embrace Imperfection Here’s a secret: your first project won’t be perfect. And that’s okay. In fact, it’s better if it isn’t. Why? Because perfection isn’t the goal. Progress is. My first project had uneven margins, clunky code, and an awkward color palette, but it taught me more than any tutorial ever could.

Think of each project as a stepping stone. Every misstep is a lesson, every flaw an opportunity to improve. It’s the process of doing, tweaking, and learning that shapes you into a better developer.

Share Your Work and Learn from Feedback Sharing your work can feel intimidating, but it’s one of the best ways to grow. Post your project on platforms like Reddit’s r/web_design or GitHub, Twitter and Linkedin. You’d be surprised how supportive the community can be!

When I first shared a project, I was nervous about judgment. Instead, I got constructive feedback and even encouragement that helped me see my potential. Engaging with others not only improves your skills but can spark new ideas and connections.

Revisit and Refine Don’t discard your early projects. They’re a snapshot of your progress and a testament to how far you’ve come. One of my favorite things to do is revisit an old project with fresh eyes. I get to refine it, polish the code, and sometimes completely redesign it.

This practice not only sharpens your skills but also reminds you of your journey. It’s incredibly rewarding to see your growth firsthand.

You’ve Got This!
Starting your first project might feel daunting, but the hardest part is taking that first step. Remember:

Start small and manageable.

Seek inspiration and learn by recreating.

Embrace mistakes—they’re proof that you’re trying.

Share your work and accept feedback.

Revisit and improve as you grow.

You’re not just building a project—you’re building yourself. The developer you aspire to be is on the other side of that first leap. Trust the process, stay curious, and don’t let fear hold you back. Your future self will look back and thank you for starting today.

Now go create something amazing! 🌟

𝗧𝗵𝗲 𝗛𝗶𝗱𝗱𝗲𝗻 𝗥𝗶𝘀𝗸𝘀 𝗼𝗳 𝗢𝘃𝗲𝗿-𝗥𝗲𝗹𝘆𝗶𝗻𝗴 𝗼𝗻 𝗔𝗜 𝗶𝗻 𝗖𝗼𝗱𝗶𝗻𝗴

Dortey Tetteh — Tue, 12 Nov 2024 10:00:00 +0000

In today’s fast-paced tech world, AI-powered tools have become incredible assets for developers. They help us complete lines, offer suggestions, and even debug parts of our code. I’ll admit, I was thrilled the first time I used AI for coding. It was like having a helpful co-pilot that made everything quicker and smoother. But as I kept working with these tools, I started noticing a downside: relying too much on AI came with its own set of challenges, some of which could actually hold me back in the long run.

𝟭. 𝗧𝗵𝗲 𝗜𝗹𝗹𝘂𝘀𝗶𝗼𝗻 𝗼𝗳 𝗠𝗮𝘀𝘁𝗲𝗿𝘆

Using AI can sometimes make us feel like coding experts, when, in reality, we’re leaning more on its suggestions than our own understanding. I remember when I first started using AI-assisted coding; I’d see a line of code pop up, and I’d accept it right away, trusting the tool more than myself. But over time, I realized that I didn’t fully understand what I was doing, especially when it came to more complex logic. I learned that it’s essential to question why AI suggests certain solutions, to dig into the "why" behind every recommendation, and to make sure I’m genuinely learning from the process.

𝟮. 𝗦𝘂𝗽𝗲𝗿𝗳𝗶𝗰𝗶𝗮𝗹 𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴

One of the best parts of coding is the challenge of solving problems, and the lessons you learn along the way. When I relied too much on AI, I noticed that I was skipping this crucial learning phase. Instead of grappling with the logic and figuring things out myself, I was letting AI fill in the blanks. It was only when I stopped to break down each suggestion and tried to write parts of the code manually that I felt my understanding deepen. Relying solely on AI made it easy to gloss over concepts that I really needed to master on my own.

𝟯. 𝗗𝗲𝗯𝘂𝗴𝗴𝗶𝗻𝗴 𝗗𝗶𝗳𝗳𝗶𝗰𝘂𝗹𝘁𝗶𝗲𝘀

This one hit home hard. Early on, I’d let AI take over too much, and when something broke, I was completely lost. Without truly knowing the ins and outs of my code, debugging became a nightmare. AI can’t teach you how to troubleshoot effectively. It can point things out, but it doesn’t replace the need for your own problem-solving skills. Debugging is a skill you only sharpen by going through the process yourself. I’ve learned now to keep AI suggestions to a minimum during debugging so I can actively work through each error and build my understanding.

In my journey, I’ve come to see AI as a powerful tool that can enhance our skills, but only if we use it wisely. By balancing AI assistance with our own problem-solving and critical thinking, we can ensure we’re not just writing code. We’re understanding it.

The Power of Healthy GitHub Contributions: More Than Just Green Boxes

Dortey Tetteh — Sat, 09 Nov 2024 14:24:52 +0000

There’s been some talk recetly about GitHub contributions, how ticking off those green boxes is just for show, and it doesn’t reflect actual learning. I get where they’re coming from, but I see it differently. Keeping a healthy contribution streak has helped me in ways I didn’t expect.

When I first started learning to code seriously, I made a decision: every day, I’d commit something and get that green box ticked. At first, it felt like a challenge. Just a way to stay accountable. But here’s what surprised me: even on days when I wasn’t feeling it, that simple goal pushed me to open VS Code, and before I knew it, I was learning. The more I committed, the more I realized that I was slowly building a routine, and with coding, that routine is key.

Sure, some people might use their GitHub streak to impress recruiters, but for me, it became a personal tracker. It’s not about showing off but creating a habit. And one thing about coding is that the more you practice, the better you get. GitHub, in this way, becomes a tool not just for visibility but for growth.

In my experience, it's not about committing huge projects every day. Sometimes, it’s small refactoring code, fixing a bug, or even just writing tests. But all those tiny bits add up. Over time, those green squares on GitHub start to reflect something bigger: consistency, dedication, and progress.
So yeah, maybe the green boxes don't guarantee you’ll be a coding genius overnight. But if it motivates you to practice, learn, and improve, then who cares? If those green boxes get me to open my IDE and sharpen my skills, then I’m all in.