How I Became Interested in Others' Work 

Suddenly, I felt like checking out how other people build websites. Why? To be honest, I wanted to really maximize the satisfaction I get from building my own websites. There are moments when I feel a bit arrogant, thinking, "Only I have this kind of sensibility!" I wanted to look at other people's work and discover some strengths I have that they don't, and then feel relative satisfaction through that comparison. 

So, I searched on Google: "Front-end developer portfolio." 

And as I clicked through the search results one by one, my excited expression quickly turned discouraged. Should I say I was overwhelmed? My work always has a certain "fingerprint" on it. When you look at my work, it feels like the entire development process is transparent: the thought process behind the design, the logic used to implement features, and the context and struggles that led to certain inspirations. This "fingerprint" feels less like dedication and more like being unsophisticated. It's that subtle disharmony between elements. 

But when I look at other people's work, it feels like there are no fingerprints. It's as if these websites naturally exist on Earth, not artificially created. There's a "professionalism" that makes them seem ready to sell. It's almost as if clients wouldn't dare disregard the developer. It's like a protective barrier that commands respect for the developer, stemming from the aura the website emits. Is this what people mean by high-quality work? Amidst such admiration, I spent about three days looking at hundreds of portfolios. I gained many insights from this, and I plan to share them frequently in future posts. 

Development and Design 

...Someone reading this might think, "This person seems to be confusing development and design." And they'd be right. I have no practical experience, and I don't plan to enter the job market as a web developer. I've always been interested in creative work, whether it's writing or music. I didn't want to just be a content uploader on platforms others use. I wanted to be a creator with the ultimate freedom, fundamentally building the platform itself. While I do use AI, it's for efficiency because of its excellent speed in finding errors, generating basic logic, and typing. My site's detailed blueprint is always in my head, so I can directly pinpoint the root cause of any problem that arises. 

Some people really emphasize distinguishing roles within the task of building a website, saying, "That's a designer's job, not a developer's main responsibility." I suppose that might be true in larger, more critical professional projects. But for me, working alone, that distinction is completely meaningless. If the site isn't showing up in searches or is slow, I have to study optimization methods, even if it's a slow process. I also have to consider accessibility for visitors (as someone with a visual impairment myself). If I feel something, whether it's a design element or a functional one, might hinder the user experience, I have to fix it myself, even if it takes time. Regarding data and security, it's not just the backend developer's role; I also have to consider intricate details like what user information needs to be disclosed legally and whether using certain content will lead to copyright issues. 

My future development logs here will contain such comprehensive content. I'll write a lot about design, front-end, and back-end, but remember that these are just the results of my own reflections from working alone, and there might be many impractical things from a professional standpoint... I haven't even created a comment section yet because I'm scared of getting hate comments. LOL. 

That's all from the owner of a website with zero visitors. 

Empty Title for Table of Contents Feature Showcase

Empty Subtitle

Just because it felt empty...