Mike Theodorou

🎸 My most favorite thing about using Typescript! ~ When you have a reusable component and it's a massively overwhelming codebase, while using those components, it is highly likely that you won't remember the required fields. ~ Maybe you provide the fields that instantly comes to your mind, but the component required some other props to be provided based on different scenarios. ~ Using Typescript with a pinch of ESLint, just solves this problem so beautifully. ~ This actually helps fasten up a progressive static frontend engineering phase. #typescript #ihatetypescript #illovetypescript #softwareengineering #frontend #frontendengineering

17

1 Comment

This came up on my feed today and boy was I excited to see great minds like Taylor Otwell, Ryan Florence, Dax and Adam Elmore getting together and talk about Web Development, where we came from and where we are headed https://lnkd.in/dXhGrjeH Really awesome to hear about the motivations behind Laravel and Remix and finally find out what a Full Stack framework actually is. #webdev #javascript #laravel #remix #DX #react

2

1 Comment

The [unsubstantiated] ghost developers conversation has me thinking: Why do employers assume they have 100% rights to the time of software engineers? If the engineer is delivering as expected, who cares how many other jobs they have? If they're not delivering as expected, that's not something to figure out via black-box "Stanford" research: your line managers should be very capable of sussing out underperforming engineers, and figuring out how to deal with them. Put another way: if you have ghost engineers, that's on you, not on the engineer.

27

10 Comments

Confession Time... #cssmademedoit As a Principal Software Engineer, you’d think I’ve left the days of battling HTML behind. But no… it’s still here. Lurking. Waiting to remind me that no matter how far we advance in tech, I’ll always be just one <div> away from insanity. HTML is like that ancient relic in your toolset: ✅ Still works ❌ Still refuses to align anything properly ✅ Always part of the project ❌ Never behaves like it should Sure, I’m out here leading software divisions, working on cutting-edge solutions, and solving complex problems. But HTML? HTML just sits there and says, “Yeah, good luck getting that button centered. 😈” No matter how high we climb in our engineering careers, we’re all forever beholden to the sacred <br> tag. So here’s to all the Principal Engineers who still find themselves whispering sweet nothings to their CSS, hoping it’ll just work for once. 🍻 #htmlstruggles #softwareengineeringlife #necessaryevils #divsanddespair #evenengineershavetosuffer

3

Are colleges/universities failing Computer Science grads in 2024? The vast majority of CS grads end up working as software engineers. But many CS grads are unable to answer basic programming questions during an interview. (We talked about OOP last week). Why should CS grads have to invest in a bootcamp or additional hands-on training to land a job after a pricy college degree? We provide these hands-on skills at no cost at HTD Talent, but we can only help so many. Has this been your experience? What do you think is behind it? Let me know in the comments.

42

19 Comments

ok so every resume builder sucks so i just coded it up in html. its simple and nice and way more malleable this way. resume builders suck nuts https://lnkd.in/eUYbGZZN

1

1 Comment

✨ “Success is never owned. It is only rented, and the rent is due every day.” – Rory Vaden This quote really stuck with me. It’s a powerful reminder that everything valuable in life and work requires daily effort: 💰 Financial security is never owned—it’s rented, and rent is due every day. 💪 Physical health is never owned—it’s rented, and rent is due every day. 🤝 Customer loyalty isn’t owned—it’s rented, and rent is due every day. ❤️ Relationships aren’t owned—they’re rented, and rent is due every day. Do you agree? #Motivation #Leadership #CustomerExperience #Family #Wellbeing #FinancialFreedom #SuccessMindset

6

Resharing this because it’s such an important point. 🌟 Titles don’t define your worth—growth and skill development do. A job title might look good on paper, but it’s the ongoing learning and evolution that truly drive career success. Not all companies are the same, and the impact you make as a mid-level developer can easily surpass the weight of a flashy title elsewhere. Stay focused on growth and keep pushing yourself forward! 🚀

1

As I'm getting back into #Angular, I'm remembering how much my brain has trouble working with RxJS Streams. But, it just occurred to me, I don't actually have to use their HttpClient module—I can use my own fetch client. All I want is Promises and AbortControllers. This is not a slight against RxJS—I know that many people are intensely in love with it. But my brain just can't deal. Resolves and rejections for HTTP requests, that's what my brain can understand. RxJS feels like more abstraction than I can handle. Maybe it has something to do with my Aphantasia.

5

6 Comments

If I wrote a book called "Typescript, RxJs, and the Angular Paradigm," based on the ideas I write here about sticking as close to "The Angular Way" as possible, including Typescript and RxJs, how many of you would buy it? Because I might have been given an opportunity to write it.

22

11 Comments

💡 Level Up Your Tailwind CSS Game! 💡 I just shared some lesser-known Tailwind CSS tricks to help make your designs more dynamic, polished, and flexible. If you’re looking to add that extra finesse, these tips are for you! Here’s what’s covered: • size- for responsive sizing with one class • group-hover for intuitive nested hover effects • focus-within for improved accessibility and interactions • peer-* to style elements based on sibling states • decoration-wavy for a unique text underline I’ve included examples to help you integrate these into your workflow easily. Check out the full post and see how these tools can enhance your Tailwind projects! 👉 https://lnkd.in/gUtX-fx7 #Tailwind #TailwindCSS #WebDevelopment #Frontend #CSS #DesignTips

2

My second feature has been PR’d! My masonry grid component is currently under review. The process has been an absolute joy to get comfortable with and figure out. Essentially, we have a components library where all components are created. We then import those components into the production-level web app, and it's there that they get used. I typically build the component from the ground up. Once it's working, I tend to refactor the code. Next, I create a Storybook component for the newly created component and then move on to tests. Before pushing my branch, I locally test it within the production app and integrate it as we envision the component would be used to ensure it works fully. Once that’s all said and done, I send out a message and wait for the green light to push. Now, I wait for my PR to be reviewed and see if it's up to par with my colleague's standards. It’s amazing to see the complexity of large, professional projects in action and navigate the process to get comfortable with it. This experience has taught me so much about project design and general “good behavior” while working in a large codebase. Not to mention, I'm super honored to say that 80% of the UI is being made by me.

25

6 Comments

Ever had a moment in your career that you wished you could rewind? Here's a post on a decision that haunted me for years. We needed a Backend Engineer for a big project. The budget was set at $140k. But, just as we were about to make the offer, things took a turn. Despite being able to offer the full $140k, our CTO decided to cut the offer to $120k. I knew it was below what the candidate deserved, but I went along with it. The candidate, needing the job, accepted the $120k. It felt like a win for our budget at the time. But the real cost of that decision was something I hadn't anticipated. As we worked closely, developing a new project over 2.5 years, the candidate became more than just a coworker. He became one of my closest friends. Never did his salary come up, nor did he receive the raise he deserved. The guilt of my initial complicity grew every day we worked together. On my last day at the company, our farewell conversation turned to his salary. I confessed my role in the initial lowball offer. His reaction was a mixture of disappointment and understanding. It hurt to know I had played a part in undervaluing him, not just as an engineer but as a friend. This experience taught me a crucial lesson: Don't let the short-term wins dictate long-term relationships. Integrity and fairness in hiring are not just about budgets, but about respect and decency. In the end, treat every professional decision as if it's personal. It's not just business; it's people's lives. Don't make offers you might live to regret.

1

I've been dabbling in HTMX recently and it fascinates me in the sense that it feels like a framework for developers who didn't like the complexity that comes with most modern JS frameworks. JS fatigue is very real, but I'm not convinced that HTMX is the solution. I do like how clean and simple it is, but personally I would rather take React and all the complexity that can come with it in exchange for the convenience of features like state management, over something like this. HTMX is a great fit for smaller brochure websites with more limited functionality, but I just can't it being a fit for modern web apps. https://htmx.org/

2

Jr. Devs, When you are sitting in that interview chair trying not to say the wrong thing and trying to remember all the stuff you’ve been told about how to interview well, don’t forget this one thing that should give you at least a little more confidence. You're not the only one being interviewed. You may think… duh, there are tons of candidates for this job. However, that’s not what I’m talking about. You are interviewing the company. Most Jr. Devs don’t think like this because, frankly, most Jr. Devs are just trying to get a job and they often don’t care or don’t consider the company or the culture they end up in. I’ve spent a lot of time on the DevMentorDave YouTube channel recently talking about mentoring and the need for it in our organizations. But that’s only one part of finding the right fit. The company is looking for candidates they think will fit what they need. Notice I said, ‘NEED”. They don’t just hire because it’s fun (it’s not). They need someone and you need to make sure they are a good fit for YOU before accepting an offer or before leaving the interview. Don’t just ask questions you found on a website or were given by a recruiter. Think about what matters to you as an employee and as an individual and ask questions that will impact how you work and impact your success and future. That level of confidence and interaction in the interview may just set you apart from the pack, even if your dev skills are the same as all the other candidates. #juniordeveloper #mentoring #interview 

12

1 Comment

🖥️ **The Wild World of Developer Interviews: When Tricky Meets Funny** 😅💻 I walked into my recent interview thinking I’d be asked the usual—JavaScript, a little React, maybe an algorithm or two. But nope. What I got was a series of tricky, mind-bending questions that left me questioning reality (and my sanity)! 😂 Here’s how it went: **Interviewer**: *“Alright, if a function was running perfectly fine for weeks and suddenly throws errors after lunch, what’s your first move?”* **Me**: “...Check if someone updated it while hangry?” 😆 Then came the mind-benders: **Interviewer**: *“Imagine you’re in a room with a computer that can only run one line of code at a time, and you can’t see the output. How would you find the bug?”* **Me**: “Take a break and come back with fresh eyes?” (Note: wasn’t the answer they wanted…😂) Next, the one I definitely didn’t see coming: **Interviewer**: *“You find yourself looking at a massive CSS file with 3,000 lines of custom styling, but you only need to change the color scheme. How do you handle this?”* **Me**: “Politely suggest a redesign…and pray for Tailwind CSS in the next sprint.” 😂 And then, the one that tripped me up: **Interviewer**: *“Say you’re working in a large team project and discover a teammate’s unoptimized code slowing down the app. What do you do?”* **Me**: “Maybe…refactor quietly?” (Lesson here: teamwork matters!) But finally, the most legendary: **Interviewer**: *“If you could remove one language from the world forever, which would it be and why?”* **Me**: *Without hesitation* “JavaScript…when it’s 3 AM and nothing’s working!” 😂 --- **Takeaways for All Job-Seeking Devs** 📌: I learned that interviews are more than technical tests—they’re full of *perspective*, *problem-solving*, and how we handle the unexpected. Here’s what I’m taking forward: 1. **Embrace the tough questions**: They’re often designed to see how you think under pressure. 2. **Expect the unexpected**: Sometimes, it’s not about the code but about your adaptability. 3. **Communication is key**: Especially when it comes to teamwork scenarios. Those “soft” questions can be the real deal! 💬 Fellow devs, have you faced any mind-bending questions? Drop them below; let’s laugh and learn together! 😂👇 #TechInterview #DeveloperJourney #CodingLife #JobHunting #ProblemSolving #SoftSkills #KeepCoding

4

1 Comment

All successfull code becomes legacy code when moving fast. It is not a bad thing. Interesting points. Although the username kind of takes the seriousness out of it 😆 Reminds me of this paragraph from "The Mythical 10x Programmer" * Perfectionism, or how to kill your productivity and bias your designs Perfectionism comes in two variants: an engineering culture of reaching the best possible measurable performance in a program, and as a personality trait. In both the instances, I see this as one of the biggest barriers for a programmer to deliver things fast. Perfectionism and fear of external judice insert a designing bias that will result in poor choices in order to refine a design only according to psychological or trivially measurable parameters, where things like robustness, simplicity, ability to deliver in time, are often never accounted for. - https://lnkd.in/dzc6heke

4

Public Assembly received 49,689.64 OP tokens from Optimism Foundation's latest RetroPGF round I helped start this developer collective over a year ago and I don't want to understate this grant being life changing for any organization. Thank you to all badgeholders for supporting Public Assembly. Learn more about RetroPGF: https://lnkd.in/eYV66veT #publicgoods #OP

3

"In the world of CSS, we see a complex negotiation of connection, where parents—Grid and Flexbox—teach their children the most profound lesson of all: how to truly care for one another." Read the full story in the latest episode of my series - "CSS is Emotional" Read, Like, Comment & Repost! "CSS is Emotional: Flexbox & Grid - A Love Story About Compromise" https://lnkd.in/dBDCs4JP #CSS #Webdev #Frontend #Programming #CSSisEmotional #CSSwithEIO #Emotion #DEVCommunity

3