DEV Community: Clarence🐼

Balancing Artistry and Efficiency: My Journey from Design to Web Development

Clarence🐼 — Fri, 15 Sep 2023 13:49:59 +0000

So… it has been 2 years since I transitioned from design to web development and I have gone from frontend to full stack (without a full-time job) and deep down, I still think and behave like a designer. It’s great but I have seen how it limits me from achieving more. You see, I have been freelancing and I’ve had a habit of taking so much time with products because I have to design the UI first and then the backend and the frontend. That has been my reason but I have come to realize that it’s been that way because the designer in me causes me to obsess over the tiniest detail which shouldn’t be that much of a thing.

You see, I was designing a flyer for my sister when she walked in and saw me manually creating patterns with the pen tool and she said “You are a perfectionist” No, I don’t think I am, I just think the tiniest detail even when not noticed has a way of bringing life to art (Art, not a web application). After she left, I kept thinking about this and thought to apply it to my next project. Lo and behold, I was working on my alma mater’s alumni directory, I designed the UI and built the whole thing while figuring out Firebase and GraphQL in less than 3 weeks all just because I decided to GO! Build, learn, launch and iterate.

“Build, learn, launch, and iterate.”
I have been noticing this as a pattern of behavior for technical founders (that’s the goal). The point is to launch as fast as possible and iterate post-launch, not the other way around and it hasn’t been that way for me. I have always been the guy who obsesses about features, beauty, and perfection. Mind you, this is not necessarily a bad thing, I think it is great to execute good UI, but I also now think that shouldn’t be the initial focus when you’re trying to get things done with speed. Perfectionism can be a double-edged sword. While it's important to pay attention to details and create a polished product, it can also lead to delays and over-engineering. Finding a balance between delivering quality and speed is crucial in the fast-paced world of web development.

You see, I run a small outlet called GreatR Works and what we try to do is help founders build their MVPs as fast as possible and I have been failing at this because, well, I am a perfectionist. You see, Understanding the specific needs of clients is essential. While some projects may require a high level of design and attention to detail, others may prioritize speed and functionality. Being able to adapt to these different requirements is a valuable skill.

From here on out, we build and learn as we go.

Best Decision I Ever Made Since I Started Coding?

Clarence🐼 — Mon, 02 May 2022 21:41:43 +0000

So it's been 2 days since I posted this Rookie Mistake? and honestly, I am wondering why I didn't take this journey from the beginning when I started learning to code. So far, I have faced the "biggest challenges" in css and javascript only to find out that it wasn't that big of a challenge in the first place.

So far, I have learned about fluid typography, basically how to use clamp() in css for responsiveness, I don't fully understand it but I know how to use it (or I now know something like that exists). After trying to centre a div here and there, I no longer have to rack my head to know where to use flex.

My biggest challenge was with responsiveness. I wrote the codes on my 24" monitor and was viewing the live version on my 15" laptop, I had the thought to switch between monitors and I realised I had mobile covered, I had tablets covered and basically my laptop screen. What happens to the 24" monitors and above? at first I tried using media query to find a middle ground but when I zoom out to assume the screen of a wider display, everything got really messy really fast. As I have learned from a lot of developers around, I took a walk and decided to browse through google till I found the fluid layout and fixed layout solution. of course I went with the fixed layout. It supported what I wanted to achieve at the time and also it was easier.

Well, there you have it. The journey so far.

I need a way to connect this series of posts. Anyway, I will be sharing more on the product as I share my progress with you'll thanks for coming.

Please drop your thoughts and advice, it's not been easy. I'd really appreciate that. Thanks

Rookie Mistake?

Clarence🐼 — Sat, 30 Apr 2022 11:49:40 +0000

So I took a risk...
Since I started learning front-end web development, I have been stalking other noob developers to see their journey and also their portfolio, and one of the things I have seen is that almost every "noob" front-end developer have the same projects on their portfolio. It's always a weather app, a bill splitting calculator or some kind of food recipe app — I don't think there is anything wrong with this, but I'd like to be a little different. so, since last night I have been thinking of a way to make my portfolio a bit different from the norm.

It finally hit me this morning. I had an idea for a platform, nothing too serious. I had done the UI/UX and I thought it would be wise to develop the platform so I reached out to a friend who is an experienced full-stack developer to assist me with the backend while reviewing my codes.

The issue I have with this decision is that almost every video and blog post I have seen on starting as a developer, they are usually against taking on full projects, it's always to start with the little things and slowly progress. I don't see anything wrong with this but I'd really like to challenge myself to do the impossible. I cannot give full details on the platform yet, but I'll try to share my progress as I go, and hopefully learn enough / have something a little unique on my portfolio to help me land my first job as a front-end developer.

Thanks for coming and please, stay tuned!