Richard Carrigan

Happy Monday LinkedIn! 👋 Just wanted to make sure all you Go Engineers out there are staying in the loop with the language on their 'X' page. If not, then click the link below and press that follow button! https://x.com/golang #gotek #golang #goprogramming #goprogramminglanguage

14

I was just ranting about this the other day lol. React is great but it's conceptually and practically heavy from an implementation perspective. Enter vanilla Javascript and DOM vs VDOM. React is great because it's uniform across the startup space. However, it does come with it's own drawbacks. Mainly in that I see bad React code that performs poorly more than I see good clean component driven code. My current code I'm working on is great. However I do wonder what it would look like if different. https://lnkd.in/gfcnAa7V

1

If celebrating software maintenance is something you want to do, you should check out the Legacy Code Rocks conference MenderCon on May 16th! I’ll be giving the opening keynote: “Community Is Just as Important as Code” Registration link is in the comments.

25

2 Comments

As a Frontend Developer You never *Hate* Styling. But I used to *hate* styling websites. No Matter how much I can do, they do not look as good as I want. Until I Know TailwindCSS. A pure gem 💎 for Developer. I can't imagine I can ever go back to CSS 🔥. #fixes #prod #SoftwareEngineer #bugs #developer #frontend #100daysofcode #programming

7

3 Comments

In over 20 years and many companies (check my profile!) of doing this, I’ve never found that there is a single “right” way of doing things. Some companies are very risk tolerant. Some are very risk averse. Some demand clean, supportable code at all times. Some just need to get it shipped as soon as possible. If you’ve only worked one or two places, you may think that the way they do things is the right way. That’s a jr dev mentality. Be open to the idea that there may be a sound reason for doing things a different way.

5

🅰️🚦➡️⚛️ Did Signals Just Land in React? "Signals" are used to manage client-side state, and recent developments suggest they could be useful in React. Last week, Daishi Kato (creator of Waku) released use-signals which aims to demonstrate how Signals can work in React. 🧑‍💻 Snippet 👇👇👇 'use client'; import { Signal, useSignal } from 'use-signals'; const counter = new Signal.State(0); const UseSignalComponent = () =〉 {  const count = useSignal(counter);  const handleInc = () =〉 counter.set(counter.get() + 1);  return (   <〉    <div〉useSignal count: {count}</div〉    <button type='button' onClick={handleInc}〉     Update count    </button〉   </〉  ); }; export default UseSignalComponent; ☝️ Signals are fundamentally different from React’s useState: 1️⃣ useState is a hook provided by React for managing state within functional components and allows you to declare a state variable and a function to update that variable. 2️⃣ Signals are event listeners or observers for handling asynchronous events or changes in data that occur outside of the component’s immediate control. As such, there’s no “setter” function defined in the Signal declaration. Whereas, with React, there is. 👩‍🏫 Conclusion: So there you go, Signals in React are possible, and it might take some time before Signals make it into native JavaScript. GitHub repository: https://lnkd.in/e7ikySR3 Full article: https://lnkd.in/exBKKqrH #react #angular #signal #signalInReact #frontend #programming

2

Ask technical candidates their current favorite tech framework/tool. Follow up questions reveal a lot: what’s the thing you hate most about it? How would you fix it? Why hasn’t the maintainers/company fixed it? How do you teach it to other people? When would you recommend not using it? If you’re really into some tech, we gotta go way past syntax. Other good questions in this vein? #meatbasedengineer

63

19 Comments

There’s something for everyone in web development in here:

8

1 Comment

Spicy question: As a beginner, is it better to first learn C# or Java? #softwareengineering #coding #programming _____ If you replied Javascript, join 25,001+ engineers: https://lnkd.in/dkJiiBnf

109

186 Comments

Here is a really great article talking about binding in JS. https://lnkd.in/gfHDDTkA

5

2 Comments

Very good guide on the efficient documentation.

3

Earlier this week I gave a talk at the Sacramento JavaScript Meetup on how you have to push through failure in order to succeed. This is a continuation of the LinkedIn version of the talk that started here: https://lnkd.in/gm2rpiEQ One of my early insights from my learning journey was that I commonly encountered people who got scared or overly frustrated when they encountered errors or new things. They were almost always significantly slower, less skilled, and a good portion of them never broke into tech. I also met some people who were completely reckless, and would just send anything. Those people also didn't do spectacularly. The connector is that both of those types of people failed to fail successfully. The first category was so scared of failure that it paralyzed them, the second cared so little they didn't stop to learn from their mistakes. The balance point between not being scared, and taking time to reflect on your mistakes is key. You HAVE to try new things, but you can't rush headlong into five new technologies, frameworks, or ideas simultaneously. Take your time, build a foundation, and use errors as a way to solidify your holistic understanding of the domain you are trying to work in. Tune in next time for a case study in the most successful software developer I hired, and what I consider the number one criteria for future hiring.

15

2 Comments

Quick question... If someone passes a folder path that does not exist to #wplizard as their plugin root, should I create that folder or throw an error?

4

3 Comments

For all of my JavaScript and TypeScript engineers out there. This is HUGE news! There is a Stage 0 TC39 proposal out there to integrate Signals and fine-grained reactivity primitives into the ECMAScript language specification. This would be especially amazing for browser and client side applications where the JavaScript runtime can be used. Many modern frameworks have been building upon their own flavors of this primitive, such as Svelete 5, Solid, Quik, and Angular. Due to not having these primitives in the language, each approach requires a compile step and reactivity graph to keep track of state. If this lands, multiple frameworks can abstract over this and/or Vanilla JS users can build reactive UI and effects without needing a framework. Amazing!!!! TC39 Proposal - https://lnkd.in/etFNAbCi #frontend #softwareengineering #signals #javascript #typescript

2

Prompt: Take this [PHP or other language] code and rewrite it into [Rust or any desired language], ensuring that functionality remains consistent. I especially like using this when writing bash scripts because 👉 I don't write bash scripts often 👉 I can never remember the syntax 👉 I know how to do it in another language What are the best use cases for AI in software development you've discovered?

7

9 Comments

I keep hearing the idea that pull requests are bad and that developers shouldn't do them. Well, to me, most of these arguments are somewhat of a straw man variety and they encourage throwing the baby out with the bathwater. Pull requests aren't the problem. Pull requests won't prevent you from doing continuous delivery. The problem is pull requests that take a long time to review and approve. This is the thing that will prevent you from doing continuous delivery. But this is a very avoidable problem. It doesn't have to be this way. In our team, PRs don't normally take long to review and things in the trunk are being updated regularly. So it was in my previous team in my previous place of work. I worked in at least three different teams where we would try to get rid of PRs to see what will happen. In all of those cases, we had to get back to doing PRs because removing them caused more problems that we were trying to solve by removing them. I get it. It may work for some teams that do pair programming all the time, which I see as the only way to keep the code quality up without the PRs. However, this approach will not suit every company and every developer. Many developers I know will find it exhausting having to pair-program all the time. Even when you pair program, PRs still have their use. Just before you push all those commits you created, you can create a PR to view all the challenges to make sure you haven't missed anything. You will not only be able to verify that no temporary code changes go in, but you will also create a nice audit trail of who made the change and who reviewed it. I even sometimes create a PR for my own changes because because it's a tool that makes a pre-push verification very convenient. PRs are just a tool. Just like any other tool, it can either be used or misused. It only causes problems when it's misused and not when it's used properly. This tool may not be useful to you, in which case you may discard it. But you may also find out that it's not as useless as some people say it is and it won't stop you from doing continuous delivery, as these people say.

38

26 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

Web-based Drag and Drop interactions present difficult challenges for accessibility. In her latest post on the GitHub blog, Kendall Gassner breaks down the challenges and explains how the team here at GitHub solved them. https://lnkd.in/d-jGPk-d

58