Reviving Custom Portfolio Websites with Human Touch

Tired of code that breaks when you change a single line? 🛠️ We’ve all been there: you open a project from six months ago and it feels like a puzzle, or you fix one small bug only to watch five unrelated things crumble. You aren't a bad developer—you just need SOLID. I’ve put together a quick primer (less than 2 minutes!) on these five design principles that turn software engineering from a guessing game into a craft. Mastering SOLID is the key to writing code that is easy to maintain, scalable, and—most importantly—actually fun to work with. In this introductory video, I cover: Why projects often "die under their own weight." The meaning behind the acronym (S.O.L.I.D.). How these principles separate coders from software architects. This is the start of a series where I’ll be breaking down one letter per video using real-world Node.js and TypeScript examples. Watch the intro here: https://lnkd.in/d-J-2sZX Stay tuned for the "S" (Single Responsibility Principle) coming next! #SoftwareEngineering #CleanCode #SOLID #TypeScript #NodeJS #Programming #WebDevelopment #SoftwareArchitecture

Hot take: validate before you build. Talk to 10 real people before writing a single line of code. If you can't find 10 people who care about your idea, you don't have a product — you have a hobby.

Knowing your place is a good place to be at. When you switch off the noise, you have to be comfortable with who and where you are. The things I want to do is my own headache. I can try to articulate and communicate via code/word, it still is very much a personal journey.

Learn Pagination in Frontend System Design Essentials Learn the two main types of pagination, their implementation, and trade-offs in our latest episode: https://lnkd.in/gvyUZnnq

You're three files into a PR review and you have no idea which one matters. Is this file touched by everyone? Has it broken CI four times this month? Who on the team has actually written code in it before? Today, answering that means digging through git blame, closed PRs, and workflow history. Reviewers spend the first half of every review on archaeology before they can think about whether the change is right. We shipped Hot File Badge. A flame icon on every file in PR review with signal worth surfacing. Hover it and you get: - Last editor and when - Churn in the last 90 days, plus CI failure count - Top contributors by additions, with ownership bars - Best reviewers by review count on that file - Recent PRs that touched it, with pass/fail dots The signal was always in your repo's history. We made it visible where you're already looking. GitHub shows you everything. We show you what matters. https://octolense.com/ #CodeReview #DeveloperExperience #SoftwareEngineering

I often am shaken away from the motivation to code (due to the size of the project) this channel helps. https://lnkd.in/e9bbPVGc

🚀 Day 14 of #LeetCodeDailyChallenge Sometimes the simplest problems teach the strongest fundamentals. 📌 Today’s problem: Longest Common Prefix 📍 Topic: Strings ⚡ Difficulty: Easy What I learned today: 🔹 Comparing multiple strings character by character 🔹 Horizontal vs Vertical scanning approaches 🔹 How sorting can simplify prefix comparison 🔹 Edge cases (empty strings, no common prefix) 🔹 Writing clean and readable string logic At first, it looked very basic… but handling different string lengths made it tricky 🤔 Then I realized — just compare characters step by step until they differ 💡 Simple idea, but powerful when applied correctly. #DSA #LeetCode #Strings #ProblemSolving #LearningInPublic #Consistency #KeepGoing

🚀 Typing Speed Game – JavaScript Project I built a Typing Speed Game using HTML, CSS, and JavaScript to practice and improve my front-end skills. The game includes: * Multiple difficulty levels * Random word generation * Timer-based gameplay * Score tracking * Restart / Play Again feature * Local storage for saving settings This project helped me strengthen my JavaScript logic, DOM manipulation, and state management https://lnkd.in/ddN9ZGvA

New statusline, what do you think? I just published a Substack article on how to set up your Claude Code statusline and fully customise it to your liking. It covers some fun gimmicks, plus genuinely useful practical tips you might not realise are possible. 👉 https://lnkd.in/e6MfsmE7

Hot take: validate your idea with real people BEFORE writing a single line of code. A 20-min conversation saves you 3 months of building something nobody wants. Talk first. Build second. Always.