Denzel Giraldo

DOM manipulation with JavaScript is a key skill for front-end developers, taking static HTML sites to interactive web apps. It's the foundation of major JS frameworks, offering a deeper understanding.

5

🚨PSA for React Developers 🚨 "Secret Internals: Use Them and You Might Get Fired!" 💼🔥 Found some undocumented features in React.js? 🤔 Beware! Using these secret internals can break your app or even land you in hot water. 😅 Stick to official docs and public APIs—your code (and your job) will thank you! 😉 #ReactJS #WebDevelopment

3

Just because you know how to create a CRUD React App doesn't mean you are a Software Engineer. "Entitled" people nowadays want a quick and overnight success with a 200k starting salary after graduation. This is what you should do. Become relevant. If you simply accept the fact that there are NO SHORTCUTS in the programming world the faster you'll become relevant and a true software engineer. Start small but be consistent. By being consistent, you'll outgrow 90+% of competition to any entry level software engineer positions. Pay the price to get the reward. Be consistent. #softwareenginner #entrylevel #jobs #success #entitled #consistent #career

14

2 Comments

Choosing The Boring JavaScript Stack for your next project is a great choice.

1

"Commit to BIG THINGS for big things to happen. They just don't happen by accident!" Rob Ocel and I spoke talk with Kent C. Dodds about his journey from Angular to ReactJS and what he's learn about JavaScript along the way. Plus hear about Kent's latest platform EpicWeb.dev! Link below 👇

9

1 Comment

I'm currently migrating my Opensource Web Projects from using Webpack to Rollup. And Vite provides the perfect tooling for that. It simplifies the Rollup setup and provides a development server with HMR. It also works perfect for building and bundling TypeScript libraries for reuse in other projects. I recorded a little tutorial on how to set everything up properly, including Dev Containers for Web Development. Here's the example project: https://lnkd.in/ez73RQcK

11

1 Comment

I have had several people reach out to me lately inquiring about coding bootcamps, from here and my YouTube. Here is how I would decide on which bootcamp you should attend: 1. Think about what technology you want to use. No point in doing a data bootcamp if you want to be a developer. 2. Understand that bootcamps are a hell of a lot to take on. There is a lot of information being thrown at you in a relatively short period. 3. We all learn differently. Reach out to the bootcamp and ask about their teaching styles and ask about any reservations you have. 4. Inquire about their career services. Most are quite lacking here so it is worth digging in and seeing what they offer. 5. Think about how much time you have to dedicate, as most are full-time. IF you have a family or other commitments you may need more support from them. What would you add?

10

11 Comments

If you are being taught React(JS) or being told React(JS) is the tip of the spear you are being lied to. ReactJS is old. It is everywhere. Learning it isn't a bad idea. It will likely land you a job in the sea of spaghetti ReactJS code bases with totally insane state layers that need your fueled up tanks of sanity (interesting enough, same fate as jQuery). And that will likely be the case for several more years. Would I work on a React(JS) code today. Yes. But not because I would want too. Or enjoy it. Or think I was using a robust and modern tool. I would do so because it has won the saturation game and that is a reality of software development. React(JS) today is a slow and inferior tool in light of, SolidJS. Objectively, as a solution alone (excluding the ecosystem argument), SolidJS is leaps and bounds superior on multiple fronts. Why is this not widely accepted? Saturation! We have been saturated in first party and third-party ecosystems and education that have cemented React(JS) into this phase of history. There is nothing wrong with admitting it. We are in the, no one gets fired for using (or sticking with) React(JS), phase. But let's be clear, React(JS) is inferior to modern solutions. Worse, it's significantly slow compared to the alternatives (hence the push to the server). In short, learn React(JS). Use React(JS). Fix React(JS). But don't fool yourself into believing that you're using the best solution. You're, objectively, not!

211

139 Comments

Lately, I'm running into an issue with senior devs not being able to pass coding screens. I'm NOT talking multi-day take home projects or leet code style questions that require dynamic programming. I'm talking the equivalent of fizzbuzz. -- tic tac toe in react -- pulling data from a data store in python -- using types in typescript ... Anyone noticing the same thing? How much prep should a senior dev really need to do these tests?

18

36 Comments

Apparently, TailwindCSS v4 removed tailwind.config.js and linked it to the CSS file instead. What are your thoughts? This could break some legacy setups... 🤔 #TailwindCSS #WebDev

14

🚀 Exciting News! 🚀 I've just published a new article on Medium: "Creating a Flip-Style Counter with React and TypeScript"! 🕰️ If you're into web development or just love the retro charm of flip clocks, this tutorial is perfect for you. In the article, I walk you through building a flip-style counter from scratch using React and TypeScript, complete with code snippets and styling tips. Whether you're a seasoned developer or just getting started, this project is a fun way to enhance your skills and add a unique element to your projects. Check it out, try it yourself, and let me know what you think! Your feedback and thoughts are always appreciated. 🙌 #React #TypeScript #WebDevelopment #Coding #Medium

6

React 19 Beta is now available and introduces a series of new changes to the React ecosystem! I've been spending some free-time diving into what these changes are and I'm going to share some highlights on LinkedIn over the next few weeks. One new addition is the new useActionState Hook — a new Hook that greatly improves how we can manage async actions during form submissions. - Define an "action" function which is executed when the form action is triggered. - Pass this "action" as the first argument to the useActionState Hook. - Access form state, form action trigger, and pending status of the action as values returned from the useActionState Hook. - Lastly, pass the form action trigger function to the new "action" prop form HTML elements can now accept. With these changes, we no longer need to handle pending states, errors, and sequential requests manually. These values can be accessed directly from the useActionState Hook! --- We're going to be sending some educational posts on React 19 to our newsletter in the next coming weeks. To get these emails directly in your inbox, feel free to sign up here — largeapps.substack.com.

47

I've been doing development for over 25 years, and if there's anything I've learned, it's that… value to the business > anything else. Good code isn't necessarily the prettiest code, but instead solves clear business problems. Even with it's initial learning curve, Next.js has allowed our engineering team Planetary to maximize our ability to provide value to our clients, and minimize time spent re-engineering age-old route handling, performance, and rendering problems. (And we can still deliver both pretty and good code.) If you haven't gotten tickets yet, I'd recommend getting virtual (or in-person!) attendance tickets to this year's Next.js Conf: https://nextjs.org/conf. I very rarely lean into talking about project architectures and frameworks, but I've been consistently impressed by what the Next.js team has been able to deliver, and I'm curious to see what they have on the docket for 2024.

19

2 Comments

No JavaScript Needed: See How CSS Can Transform Your Web Designs! #NoJavaScriptNeeded #CSSTransforms #WebDesignMagic #FrontendDev #WebDevTips

9

Week 7 of the Northcoders full-stack JavaScript developer boot camp has been an absolute blast. The task for this week was to build an API for a news server using Express.js and PostgreSQL, connect it to Supabase, and deploy it using Render to make it accessible online. I have learned how to write secure SQL queries that are protected from SQL injection, and how to validate queries to ensure that the data exists, and how to seed and query databases. I've also come to understand the importance of separating concerns and properly handling errors where necessary. In the weeks leading up to this, I learned how the model, view, and controller (MVC) architecture works, how to apply test-driven development (TDD), how to use a tool called Insomnia to check endpoints, how queries and parameters can be tested, and how integration testing with Jest and Supertest is done. I'm excited about taking all these skills and applying them to build a full-stack app in the upcoming weeks. It will be a great opportunity to combine everything I've learned into one full-stack app. The repository can be viewed by going to the link below. https://lnkd.in/gt97TEwX

11