Coder Legion - Recent posts tagged problem-solving

RESUME / CV BUILDER WEBAPP

Mon, 03 Aug 2026 06:00:45 +0000

For the past 2 weeks I have been upgrading and testing my resume builder website.
I sent this to a lot of people and most of them gave me their feedbacks, some were pleasant some weren’t. At some point I felt a little frustrated because what I was building wasn’t for me but for people to use and if those same people aren’t satisfied with it then there’s no point in letting it out to the public.

So what I did was, after getting their feedbacks I often ask for their opinion on the area that needs improvements and that was how I got to finally finish the project.

Now I learnt a lot in this project, though this is purely frontend but I just wanted to say, it’s very necessary for one to send out his work to others to test before he finally makes it public especially as a starting developer, although I do this all the time but this particular one taught me alot of lessons.

Now these upgraded Resume Builder carries a lot of features and with the same I deal in which I built it in the first place.

The ideal: I wanted it to be so easy and understandable that children or people who haven’t seen how it is or how to make one can actually use it along with professionals.
Also this is not just a resume builder but CV and Resume Builder.

I used resume because it was the first thing that came to my mind at the beginning of development and I was hunting for jobs then.

The Features: multiple templates, two option downloadable PDF (visual and ATS), ATS friendly, Autosave options but the thing with this is that because it’s frontend and no database integration once it auto saved you can only access your saved work on the specific browser you saved it, let’s say you opened the link with google chrome you can only access your saved work/history in google chrome, but once you open the link with another browser your saved work won’t be there unless you already have one on the browser.
It’s responsive, now the downloadable PDF option visual means your downloaded pdf will display along the template you chose, but ATS means it will be in plain white and black.

The other features are that your links can be accessed in the PDF, if you added any link to your resume/cv and sent to the employer he/she can access it by clicking them on the PDF, be it email, phone number, gmail, LinkedIn, behance, dribble, Instagram etc.

There are also other amazing features but I will let you explore them and tell me what you think.

The Death of Stack Overflow?

Mon, 27 Jul 2026 07:38:05 +0000

Remember when solving a problem meant:

Searching Stack Overflow
Reading documentation
Comparing multiple solutions
Understanding why something worked

Now the workflow is often:

"Ask AI → Copy code → Move on"

AI is amazing, but I wonder if we are losing one of the most important developer skills: problem investigation.

Great developers were never just good at writing code. They were good at finding answers.

Will AI make us better problem solvers, or make us less curious?

My Resume Builder

Mon, 01 Jun 2026 10:45:39 +0000

My Resume Builder Website‼️

BDevC Work App Help

This is just the name I could come up with, lol. This website was developed with React js + TypeScript SWC + Tailwind css

This website is designed to house anything that helps you prepare for your job applications or job huntings, but the resume builder is the only thing available on it for now, but there would be further expansions and updates as time goes on.

This website is meant to help the working class or anybody to create their own Resume / Curriculum Vitae which would be automatically organised and structured for them.

The designs are functioning effectively and are responsive, so you can use it with your smart phones, tablets, laptops, bigger screens etc or any device that can access the internet.

You can copy or download your resume / CV when you are done, your choice.

This website is customize so that any changes you make it immediately reflects, just like typing in microsoft word only difference is that you don't need to press enter to move to the next line or other things because this website is designed to automatically organise your work for you when you are done without needing to do them yourself.

This is a temporal appearance as new improvements and updates would be done from time to time.

Here is the link to it so check it out and make proper use of it.

https://bdevc-work-app-help.netlify.app/

Developers don’t have a productivity problem. They have a memory problem.

Wed, 08 Apr 2026 16:39:39 +0000

Every developer knows this feeling. You’re deep in a build, everything is going well, you’re in flow state… then suddenly you need something you’ve already written before. A snippet, an idea, a fix, a link, anything.

You know you’ve seen it somewhere. You just don’t know where. So you stop coding and start searching. Discord, Notion, old projects, random files, browser bookmarks. Tabs start to pile up, whilst your focus slowly disappears while you try and retrace you own steps.

And when you find it, the momentum is gone. I used to think this was an inevitable part of being a developer, but over time I realised something important: I wasn’t losing code, I was losing context. And that is a much bigger problem.

The real issue isn't writing code. Developers don’t usually struggle because they can’t build things. Most of the time, the actual coding isn’t the hard part. The real issue is everything around it: the fragments of information that never stay in one place. Snippets end up in Discord messages or random files. Ideas get dumped into notes apps, just to be forgotten, or useful links are buried in your browser history. Fixes live inside old projects you never think to open again.

We don’t have a skill issue: we have a fragmentation problem, which quietly is slowing everything down. Not obviously, but through small, constant interruptions that break focus and force you to rediscover things you’ve already solved before.

At some point, I did what most developers end up doing: I tried to fix my workflow, using Notion, Obsidian, GitHub Gists even bookmarks, folder systems and even “just being more organised”. They all worked at first. But they all broke for the exact same reason. They require you to put in effort at the exact moment you don’t have any.

When you’re in flow, you’re not thinking about organisation, you’re thinking about solving the problem that’s in front of you. So, everything gets dumped wherever it’s fastest to continue, eventually turning temporary storage into permanent chaos. So, you don’t end up with one perfect system, you end up with 10 half-broken ones.

The real shift occurred when I realised I didn’t need another notes app, with more structure, or stricter habits. I needed something that could work with the way developers actually think whilst working: something that could capture context without interrupting it. This is how DevFlow came about.

DevFlow is a developer-focused second brain that is designed around one simple principle: your work should have a memory layer. Not a separate system that you have to maintain, but something that sits quietly underneath everything you do, capturing what matters as you go.

DevFlow lets you save snippets, notes, ideas and links instantly without breaking your flow. Everything you capture is automatically organised by project, so your work stays grouped naturally, instead of scattered across multiple unrelated folders.

You can search everything you’ve saved in milliseconds, filter by project, and quickly retrieve anything you’ve written before. The goal isn’t to add another place to store things, it is to remove the friction between thinking something and saving it. Think of it like Notion, GitHub Gists and Recast combined, but rebuilt specifically for developers who want to stay in flow state.

Most tools assume that you have time to organise your thoughts properly. Developers don’t. Notion is powerful, but it’s too slow and structured for quick capture. Gists are useful but isolated. Notes apps are flexible, but can become messy very quickly.

The problem isn’t that these tools are bad, but that they aren’t designed for real-time thinking while coding. They sit outside of your workflow instead of in it.

This isn’t just about saving snippets, or organising notes, it is about protecting your flow state, removing the moment where you have to step back and ask “Where did I put that?” It is about ensuring ideas don’t disappear just because you had to focus on something else, because in development, the biggest loss isn’t bad code, it’s forgotten progress.

Right now, DevFlow is in its early stage. I’m building the MVP around a few core ideas: projects, instant capture, fast search, and a clean dashboard. But my long-term vision is much bigger.

DevFlow is moving towards becoming a full memory layer for developers, which includes semantic searching across everything you’ve ever saves, automatic tagging, deeper connections between ideas and integrations with tools like VSCode and browsers, so you can capture anything instantly.

I’m currently validating the idea and building the first version of DevFlow. If you’ve ever lost something you knew you saved, or felt like your workflow is more scattered than it should be, you probably understand why this matters.

I’m opening up early access as I build, so if you want to follow along or try it when it’s ready, you can join the waitlist here.

DevFlow

We don’t need more tools to store information, we need better systems for remembering it. That is what DevFlow is trying to become: a memory layer for developers so you can stay focused on building, not searching for what you already built.

Solo Creation: Games and the Psychology Behind Them

Fri, 16 Jan 2026 08:56:00 +0000

Hi, I'm Lucas from Poland :) I work primarily as a solo creator.
Most people know me from the technical side - building games, systems, prototypes, and shipping projects on my own.

But over the years, I’ve become just as interested in the psychological side of solo creation.

What happens when you’re alone with decisions for too long?
How motivation changes after the initial excitement fades?
Why some projects slowly die - not because of lack of skill, but because of mental friction, fatigue, or loss of meaning?

Solo game development isn’t just about tools and code. It’s a long-term mental process: identity, resilience, energy, doubt, and learning how to stay in the game long enough to finish something.

These questions now influence how I build games, how I structure my work, and how I think about creative sustainability.

I’m still making games solo. I’m just paying more attention to what’s happening inside the creator, not only inside the project.

Abstraction: The Unsung Superpower for IT Professionals.

Sun, 07 Dec 2025 19:43:39 +0000

If you’ve ever tried to debug a modern system with multiple layers of dependencies, APIs, and databases, you know the feeling of being completely overwhelmed. Now imagine trying to do it without any tools to simplify the chaos. Enter abstraction, the secret superpower of every effective IT professional.

At its core, abstraction is the art of hiding complex implementation details while exposing a simple, usable interface. It’s a skill that allows IT professionals, from developers to network engineers, to manage complexity, design scalable systems, and collaborate effectively. In today’s tech landscape, understanding abstraction isn’t optional; it’s essential.

The Problem of Complexity

Modern IT systems are incredibly intricate. They span hardware layers, operating systems, frameworks, APIs, databases, cloud services, and more. The human brain, however, has limits, we can only process so much detail at once. Without abstraction, even simple tasks become overwhelming.
Think of debugging a system without abstraction like trying to repair a car by tracking every molecule in the engine. It’s inefficient, exhausting, and almost guaranteed to fail.

Abstraction in Practice

Abstraction isn’t just a theoretical concept; it’s everywhere in IT. Here are some practical examples:

Programming (OOP & Functions)
In Object-Oriented Programming (OOP), classes and interfaces define what an object does without exposing how it does it.
Example: A Payment Processor class might have a processPayment() method. As a developer, you just call processPayment(), you don’t need to understand the intricacies of credit card gateway integrations happening behind the scenes.

Databases

Structured Query Language (SQL) is a high-level abstraction over the physical storage and indexing mechanisms of a database. Developers can write queries like SELECT * FROM customers WHERE active = 1 without knowing how the database stores the data or retrieves it efficiently. This allows them to focus on business logic rather than implementation details.

Networking (OSI Model)

Networking is the ultimate example of layered abstraction. The OSI model separates concerns into seven layers, from Physical to Application. A developer working at the Application Layer doesn’t need to worry about electrical signals, packet routing, or hardware specifics, those details are handled at the lower layers.

APIs

Application Programming Interfaces (APIs) are contracts that provide simplified access to complex systems. For instance, integrating Stripe for payment processing or Google Maps for location services allows developers to use advanced functionality without touching the underlying backend code. APIs are abstraction in action.

Why Abstraction Matters for IT Professionals

Managing Complexity: Simplifies interactions with complex systems.
You can focus on the rather than the how.
System Design: Encourages modularity, loose coupling, and clean
separation of concerns. Components can be swapped or upgraded
without breaking the system.
Efficiency & Reusability: Abstracted code and services can be reused
across projects, saving time and reducing errors.
Maintainability: Encapsulation isolates changes and bugs, making
debugging and updates safer.
Collaboration: Teams can work on different modules simultaneously
without interference, thanks to well-defined abstract interfaces.

The Caveat: Leaky Abstractions

Abstractions aren’t perfect. Sometimes, hidden details “leak” into the surface. A poorly performing API, unexpected database behaviour, or a network bottleneck might require digging into the layers you thought were hidden. Experienced IT professionals balance trust in abstraction with enough curiosity and knowledge to troubleshoot when things go wrong.

Conclusion

In the fast-evolving world of IT, abstraction isn’t just a programming trick, it’s a defining skill of senior, effective professionals. It allows you to manage complexity, design scalable systems, and work collaboratively without getting lost in the details.
So the next time you write a class, use an API, or design a layered system, remember: abstraction isn’t just hiding complexity, it’s giving you superpowers to focus on what truly matters.