Adrian Hajdin

Ever faced a moment where you knew the answers but couldn't deliver? Here's my story of a Wordle app challenge... A few years ago, I applied for a frontend developer role at one of the top companies in Serbia. Part of the interview involved creating a Wordle-like app in React during a live coding session. I had 2 hours and felt confident - I knew React well. But then, for reasons I couldn't explain, I froze. It wasn’t stage fright or lack of knowledge. The interviewers were supportive, and I could use online resources, but nothing clicked. By the end of the session, I had nothing to show. That night, I was determined to prove to myself I could do it. I opened my laptop and, in less than two hours, built the Wordle app from scratch, using React + Vanilla JS + CSS. Recently, I decided to revisit this project with a fresh perspective - this time using React + TypeScript + Chakra UI - and challenged myself to the same 2-hour time limit. Here’s the result: 🎮 App: https://lnkd.in/gNhyypaW 💻 Source Code: https://lnkd.in/gqasj2MC I’d love to hear your thoughts - how can I improve it? Or better yet, submit a pull request! This experience taught me an important lesson: growth is about persistence and learning from your challenges.

14

I’ve reviewed 100+ CVs — this one issue is everywhere. Achievements lack impact and measurable results. Too often I see CVs filled with descriptions of tasks instead of clear, result-driven accomplishments. "Optimized payment page performance" So what? It’s hard to see the value you brought. - How many seconds did you shave off the loading time? - How did it impact user satisfaction and conversion rates? - How much more revenue did it generate? If I can’t quickly understand the impact of your work, I’ll move on to the next candidate. Your resume’s job is to get you an interview, not just fill up someone’s inbox. Here's what you want: "Cut 1.3 seconds from payment page loading time, resulting in a 15% increase in conversion rates, which boosted company revenue by $500,000 annually." Don’t just describe what you did—show the difference it made. Numbers speak louder than words, so use them to highlight your contributions. Here’s a simple formula to keep in mind: - Action: What did you do? (e.g., optimized, developed, led) - Result: What was the outcome? (e.g., increased, reduced, improved) - Impact: How did it benefit the company? (e.g., boosted revenue, cut costs, enhanced efficiency) Every bullet point on your resume should tell a story of how you made a difference. This approach not only shows your skills but also demonstrates your ability to deliver real, measurable results. Your CV is your first impression—make it impossible to ignore.

47

23 Comments

𝗧𝗵𝗲 𝗜𝗻𝗻𝗲𝗿 𝗖𝗼𝗿𝗲 𝗼𝗳 𝗙𝗿𝗼𝗻𝘁-𝗲𝗻𝗱 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁: 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻 💬👨‍💻 Does your frontend developers communicate well with your team? Read our article and understand the essential role of effective communication between front-end developers and their team members. 📰Read the full article here: https://lnkd.in/g6i2VRCp Got questions for us? Send us a message! 📩 www.ingenuity.ph/ #FrontendDevelopment #Communication #Team

10

The Coding Mistake That Almost Cost Me Everything Payment Loophole Alert How I Almost Lost Everything Because of a Simple Oversight I made one of the biggest coding mistakes of my life and it could have COST ME EVERYTHING. But then a stranger, Panashe Mapika, reached out and saved me. Here's what I learned from this close call: 1. Always Triple-Check Payment Systems Before Deploying 2. Never Assume Your Code is Flawless 3. A Simple Loophole Can Be EXTREMELY COSTLY Here are the numbers that make it real: - 10% of my users could have taken advantage of the loophole - 50% of my profits could have been lost forever - 1 minute of reflection could have saved me ALL of this But here's the thing: I would have never known about the issue if it weren't for Panashe. And that's what makes this community on LinkedIn so powerful. So, how would you handle a similar situation? Have you ever had a stranger save you from a potentially DISASTROUS mistake? Take the risk or loose the chance #TechSupport #CodingCommunity #LearningFromMistakes

104

45 Comments

Last week, I had one of those moments. My friends and I were out for dinner, and when it came time to split the bill, we turned to our usual app. But things quickly got messy – limited features unless paid, clunky interfaces, and a group chat full of confusion. That night, we thought: Why does something so simple feel so hard? Instead of just complaining, I decided to take action. 💡 This is the start of something new: an app built to make bill-splitting intuitive, fair, and (dare I say it) fun! 🚀 ✅ Easy bill-splitting for meals, trips, rent, and beyond. ✅ Real-time clarity on who owes what – no guessing games. ✅ A smooth, user-friendly experience designed with YOU in mind. We are building it in public because I know I’m not alone in this frustration. If you’ve ever struggled with other bill-splitting apps, I’d love to have you join me on this journey. 📋 Sign up for Early Access: https://fairsplits.in Help shape the app you’ll love using. Your feedback will be the foundation of something better. Let’s make awkward bill-splitting a thing of the past! Ben George Arun Mathew Vineeth Abraham Shaji #FromProblemToProduct #BuildingInPublic #EarlyAccess #BillSplitting #StartupJourney

57

6 Comments

Feature flags, ReactJS vs SolidJS and Tailwind were the topics of discussion at the last Helsinki JavaScript Meetup. I got inspired and humbled by informative and practical discussions, and who doesn't love pizza? A big shoutout to Toughbyte for organizing this together with our very hospitable hosts SOK 🫶. #helsinkijs #sok #javascript #helsinki #devlife #techtalks

20

Frontend software development is much more difficult than most people think. I would compare it to systems-level engineering. It gets a reputation of being "easier" because of the perceived notion that the consequences of bad code are not as high as when programming at a systems level. That can certainly be true - it's much more manageable to handle a browser crashing than a computer crashing because you wrote to the wrong space in memory. However, good Javascript takes just as much skill and care - browsers can just handle more unsafe code than an operating system can. Frontend engineering can be so challenging because of the nuances between browsers. You're still engineering for different systems that handle internal memory, graphics, etc in many different ways. I would argue that Javascript and the frontend ecosystem is more accessible from a beginner standpoint than C++ or C, but it is still just as difficult to fully master once you've learned the basics. There is so much under the hood of Javascript with rendering engines, DOM manipulation, transpiling, memory, local storage, and so much more in the ecosystem to make it work in all the different browsers that users can possibly have. #softwaredevelopment #javascript

2

📣 Now in print! 📣 React In Depth, by ✨ Morten Barklund. 📚 Looking for a #React job? Morten's new book covers advanced #Reactjs topics and modern best practices, with full coverage of the latest features and changes to the React ecosystem. The book is now available in print. Thank you for the wonderful quote, Theo Despoudis. ❤️ #ManningBooks #LearnwithManning

20

So I have deep dived into bolt.new, which in my opinion is the best AI tool for app development currently. What I noticed is, it's amazing when you have little code and want to add a lot of code, so in the beginning of the project when you are setting up everything. Bolt will give you a lot out of the box, I really like how it gives you are really decent design without even specifying anything, something many engineers struggle with. Where I think it is not super useful yet is where you are in a more mature phase of a project and you are changing smaller details in multiple files, this is when Bolt sometimes does changes that were never requested, and it makes it difficult to undo those unintended changes and it also makes it expensive as it is using many tokens to change something that needs to be undone later. Maybe there is a way of avoiding this issue but I haven't figure it out yet.

9

When I was starting with front-end development 7 years ago... Everything was messy. Literally, I didn't know where to start. And meanwhile, thousands of developers were growing excellent careers. - High salaries - Massive careers - Important networks But everything I tried didn't work. I was lost. Then, I started to reverse-engineer some of the best front-end devs I knew. What did they do differently to learn front-end development? After going deep into their past, it started to click. So armed with a strong roadmap, I recreated my learning journey. In the next 6 months, I was hired as a front-end developer. It's completely changed my career. So, recently, I shared the front-end developer roadmap that I used in a newsletter issue. You can read it for free here: https://lnkd.in/dvEAsPpS

159

27 Comments

This week was released a new Giraffe version: 7.0.2. The highlights of this new version are:   - Code was made more consistent style-wise with the usage of Fantomas. - Code is now a bit more safe, since we're gracefully handling option unwrapping for Preconditional.fs. Thanks ionide.Analyzers for capturing this. - New request guards/limitation were added to check for Accept, Content-Type and Content-Length headers. Documentation is updated, and new automated tests were added. - Maintainers information was updated. - Fixed the incorrect dispose of the request body from the HttpContext object, when using the ReadBodyFromRequestAsync extension method. New tests were added to validate this fix.   If you're interested, more detailed information can be found at the release notes: https://lnkd.in/dWdhEcKk.   #fsharp #dotnet #giraffe #foss #opensource

23

Last Friday I published my second blog article, called „Tailwind CSS Tips Every Developer Should Know“, which became the top post of the month on r/tailwindcss in less than 24 hours. I've been using Tailwind CSS in every web project I've worked on for the last 2 years, as it saves me a huge amount of time when it comes to #webdesign. During my time at moskito - Kreative Strateg:innen, I was able to develop several landing pages and microsites, which gave me the opportunity to discover the ins and outs of the CSS framework. In this article I've summarised many of the things I've learnt over the years, so if you're a developer and want to give Tailwind CSS a try, maybe there's something for you too. I would love to hear what you have learnt or your favorite tips and tricks! #webdevelopment #responsivewebdesign #webdesigninspiration #HTML #CSS #UI #UX

12

1 Comment

Finally, our big launch is happening today! Before I explain what’s in it, I just want to give a big shoutout to our engineering and product team for making this massive feat possible. We worked around the clock for the past 6 months to bring the biggest product update yet: our DCP platform. What is it, you ask? Our new Demand Conversion Platform provides the perfect recipe that converts marketing demand into qualified pipeline that sales loves. Four major updates make this possible: 🌟 Chat Our brand-new chatbot is here! Now, you can engage with website visitors, route them to an available rep, or let them schedule a meeting instantly—all within Chili Piper. It’s time to simplify your stack and get rid of standalone chat solutions. 📅 ChiliCal Meet ChiliCal, the only smart scheduler built specifically for customer-facing reps. You’ll love features like automatic timezone detection, prioritized meetings, and one-click scheduling. 🔄 Shared Routing Logic Managing teams and routing logic across multiple tools is the worst. But with our new shared routing logic, you can repurpose user groups and settings across all Chili Piper products. This means fewer headaches, fewer mistakes, and a much smoother process. 📊 Consolidated Reporting Bring all your demand conversion data into one place. Now, you get a clear, accurate picture of your lead conversion across your entire funnel. Spot leaks easily and make data-driven decisions to boost conversions. ☝️ Yup, all of this in one platform at a fraction of the cost of other solutions. — We also created an entire playbook for your team, with tips from more than 50 revenue leaders, to help you convert demand. Start converting demand: https://lnkd.in/dJ2ft4kW 

50

back then: No jQuery? u bad. then: jQuery?? why? back then: Yay, PHP, server-side! then: lol you better be making an AJAX SPA! ... And that's where everyone is now: going back to SSR, because this is the new correct. All the times before we were wrong but finally we're right. An excellent developer will be amazed by current technology but not blind by convinction. An excellent developer will both acknowledge the current changes but at the same time look at them with necessary critical viewpoints. Criticism and the search for the better will improve technology, not blind acceptance. You can choose to stay in acceptance or healthy criticism. #webdev #development #programming

3

From A Failure to Senior Front-End Developer... (in 5 years) I was a failure when studying for my degree... I struggled with coding exams, battled with self-doubt, and faced ridicule from classmates who doubted my potential in this field. In 5 years, I become a Senior Front-End Developer, working on big projects with millions of active users. Here are 3 takeaways: - Believe in Yourself - Consistency is Key - Never Stop Learning Tomorrow, I'll show 3,383 people my complete journey and how to overcome obstacles and reach new heights in front-end development. If you want to kickstart your front-end career journey, don't miss it! Subscribe to Saturday Front-End newsletter (link in my profile)

382

44 Comments