Dale St. Marthe

My article that I wrote for an Upwork job is on daily.dev as top voted for the week. You can check the article here: https://dly.to/LzBC8Kzg8Uv :))

4

1 Comment

I got my first job after learning HTML/CSS and some basic JS/Vue for about ~6 months. It was a student position, but I got it because of my portfolio + projects (even though they were bad) that showed my passion. It's true that the job market has changed since then, and I do believe it's more difficult to land an entry level front-end job today - but it's definitely not impossible. Channel your learning, focus on the basics, and build a lot of projects. Then toss the best of them into a neat portfolio. Most of the learning will happen on the job, so the key is to stand out and get your foot in the door somewhere. Then you can always improve and level up from there. 🔥

614

37 Comments

CSS/TS/Javascript UI Mini Software in Meta Horizon! In two days, with help, I’ve made two old Windows style programs for Mobile/VR. These simple scripts use a combination of languages to enact a mini-game housed in one UI window. I’m building a mini-OS. 😂 #programming #javascript #meta #metaverse #coding

3

Day 48 of #100daysofALXSE 📈 Progress Overview: - Time Spent: 3 hour 💡 What I Learned: After submitting my HTML/CSS Odin Project Landing Page yesterday, my mentor noticed how far my class names are from best practices. Though my web page looks 80% similar to the sample I am given to replicate, he insisted I must embrace the Manifesto for Software Craftsmanship way, part of which is not only creating working software but also WELL CRAFTED. I continue today to read and practice more on naming conventions for organizing CSS class names. Though I've come across a freeCodeCamp article detailing the BEM Naming Convention, I plan to go deeper into my search 📚 Resource Used: https://lnkd.in/d9sEsEnX 🗓️ Plan for Today: Learning never stops. #CodeNewbie #LearningInPublic #CodingJourney #ALX_SE #100daysofALXSE #DoHardThings

5

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

If I had to name a topic that isn't typically discussed during job interviews for developer positions but is crucial in every job I've had, I'd probably think first about 𝐦𝐚𝐢𝐧𝐭𝐞𝐧𝐚𝐧𝐜𝐞. Honestly, after thinking about all my interviews, I can't recall a time when this topic was even touched upon... For every project/product that takes longer than a few months to develop, sooner or later the question arises whether it's time to pause the development of all new features and instead fix things a bit or continue forward. Sometimes this happens due to not quite right choices made at the beginning of the project. Sometimes it's because a programming language or some specialized library becomes unsupported by the operating system. Or perhaps some service that the product depends on will no longer be supported... what to do then with that functionality? Essentially, there can be multiple such situations. And although those who don't know programming or know less may imagine that all those good senior developers can easily program it and everything will work fine forever, the truth is that there's no developer who can accurately predict when some part of a larger product/project will start malfunctioning. Perhaps there are better chances when creating programs for a Windows operating system - because an even larger portion of programs written even 30 years ago still work without major issues, but those chances start dwindling as the product/project becomes more related to the internet or its functionality is directly tied to security or another area where essentially a few parties compete (heh, what tricks those IT specialists don't come up with?!), one trying to find ways to circumvent the solutions of the other side, and then the other side has to fix again - to find better ways. Good developers who are moving towards the senior side only increase the chances that the decisions made at the beginning of product/project development will last longer. But they don't safeguard against it. In an ideal world, there should always be enough time and budget for developers when such problems arise to fix them, but, unfortunately, the truth is that despite better management ideas emerging all the time, foreseeing enough resources for solving such problems is still impossible. If the team working on the project/product is small, usually such problems emerge quite close to the time they need to be solved. Moreover, sometimes several team members have different visions/understandings of how all this should be addressed. And each of those options has its pros and cons. So it can be said that sometimes there may be a clear path on how everything should be addressed and sometimes there may not be, and then the question is "what then?". Although there's no single clear answer on this topic, I would say it's much more useful than those traditional popular interview questions like "list as many programming patterns as possible".

3

2 Comments

Great interview between Brian Jenney and Vanessa V. with a lot of great nuggets! Some of my favorite tidbits: - If you're an introvert, you can pick and choose the people you WANT to talk to (which could make all the difference in networking!) - Find the learning tools that work for the way YOU learn (Thanks for the Scrimba rec!) - Finding a junior role is not about a specific skill or language or tool but rather your personality and aptitude (can they see working with you? can they see you GROWING?) There are no hacks or secret passwords to getting a job in tech: sometimes it's just consistently showing up, learning new skills, and getting experience (wherever and however you can 😎 ) If you want to listen, I'll put the Spotify link in the comments but highly recommend checking these peeps out!

8

2 Comments

Learn About the CSS gap Property! Want an easy way to space out items in your web designs? Check out my latest article on the CSS gap property! It's a simple tool that makes creating clean layouts much easier. Read the full guide here: https://lnkd.in/gqcFujBA Have you tried using “gap”? Let me know in the comments! #Css #WebDesing #frontendDevelopment

4

PSA junior devs You need to know the basics: HTML, CSS, JavaScript I’ve interviewed 10+ times (relatively small sample size, I know) Built projects using: React, Next, Redux, Vue, Nuxt, Astro, Hugo, GSAP, Tailwind, Bootstrap … And no one has ever asked me anything significant about those tools (aside from the preference between React or Vue, and Tailwind still being controversial for adoption for some reason…) I imagine all of these tools are useful to include on my resume, and they are good talking points But when it comes down to the technical portion of interviews, it’s always been back to basics (at least for my personal experience and probably the front end heavy early career roles I’m looking at. YMMV) Study up if you’re lucky enough to have landed an interview To anyone reading this, feel free to reach out with any questions about interview prep / my experiences / general support Breaking into tech is hard, so let me know how I can help

41

10 Comments

Just claimed my badges on O'Reilly! Their Tailwind CSS course was fantastic, and I highly recommend it for anyone looking to learn Tailwind. It covers everything you need to know to get started building beautiful and responsive UIs. #tailwind #professionaldevelopment #learning #tech

12

1 Comment

🎸 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

18

1 Comment

I was sitting here stretching after my run, watching some YouTube videos, as you do…a new one from Kyle (Webdev Simplified) popped up about implicit tests. It references this article: https://lnkd.in/e6MQgxr9 Had a quick read, and I found myself having done the opposite in some of the tests I’ve been writing. I had a quick flashback to one specific one where I had plenty of .toBeInTheDocument() when the assertion after tests for the thing being present anyway. Here’s to better tests. #frontenddevelopment #testing #tdd #webdevelopment #reacttesting

1

So many Developers come to me with the same problem: "I'm unhappy in my current job, but I don't know what would make me happier." It's a really overwhelming position to be in. How can you start a job search if you don't know what you're looking for? If you're in a similar position, here's what I always suggest: 1️⃣ Make a spreadsheet or grab a piece of paper. 2️⃣ Separate the page into: - Fixed salary - Bonuses & perks - Work-life balance - Setup (office/hybrid/remote) - Culture - Colleagues - Management - Progression/growth opportunities - Challenge - Overall happiness 3️⃣ Then, rank each category out of 10, and think about what's behind your scores. By breaking your job into bite-sized pieces and inspecting each one, you'll be one step closer to identifying what's missing from your current role and what you'd like to gain from your next one. I hope this is helpful, and if you need any support, you know where to find me! 🙂 #MobileDevelopers #SoftwareDevelopers #AppDevelopers

4

1 Comment

🌟 Webpack Got You Stuck? No Worries! Debugging Like a Boss 🚀 Ever feel like Webpack throws cryptic error messages at you? Fear not, fellow coders! Today (Day 135 of #365DaysOfCode), I levelled up my Webpack skills by tackling debugging and troubleshooting common issues. Now I can: Decode Webpack's Messages: Interpret error and warning messages like a pro, identifying problems quickly. Configuration Confidence: Adjust loader and plugin configurations to resolve issues. I even simulated a build error to practice fixing it firsthand! Problem-Solving Prowess: This experience sharpened my problem-solving skills, equipping me to tackle future build challenges efficiently. Tomorrow's Adventure: Get ready, React! I'm excited to explore integrating TypeScript with Webpack, leveraging my TypeScript knowledge for even more robust and reliable builds. What are your best tips for debugging Webpack builds? Share your experiences in the comments. #Day135 #DailyLearning #Webpack #Debugging #Troubleshooting #React #TypeScript #365DaysOfCode

25

Bringing Your #React #App to Life: A Beginner's Guide to Server-Side Rendering - Enhance your coding expertise with @ava-patel on OnlyCoders.net Follow @ava-patel and Read More at https://lnkd.in/etwfgC7e #programming  #softwaredeveloper #softwareengineer #100daysofcodechallenge #webdevelopment

7