Peter Mouland

Node.js now supports TypeScript. Wrote up a full summary (posted below). Here's the juiciest bit - the TSConfig you'll need to run it:

Dear @elonmusk , Let me help you out here. I understand that you are not a people person, and this isn't easy for you. But you're getting ratioed on your own site. So let me offer a suggestion for How to Disagree with People (in a way they can hear). It'll be relatively painless, I promise. I'm not going to call you any hurtful names. First of all, it's okay that you don't already understand this. You're not a people person. You build rocket ships. You just want to build rocket ships. That's your mission in life. Why won't people get out of your way and stop interfering with the stuff you need to build the rocket ships? Don't they understand how important the rocket ships are? This is the entire zarking future of humanity we are talking about! Everybody was excited about this two zarking seconds ago! Now you're telling them what it takes, and suddenly everyone is angry? Why won't they understand your problem? Okay, so here's lesson one, of one. This is the only point I have to make here, and the only thing you need to understand. Lesson One, of One: People are generally not willing to understand or care about your problem, until you show that you understand and care about their problem. That's it. That's everything. That's the whole secret to winning friends and influencing people and not getting ratioed. Here's how you do it: Articulate their concerns to them, in your own words, to show that you understand what they are worried about, or afraid of. Don't tell them they are wrong. Don't tell them they don't know what they are talking about. Don't tell them they owe you their trust. Just tell them, in your own words, what their problem is. You will know you have done this correctly when they calm down and start being willing to listen. If they don't, and they keep telling you their problem, that means you didn't fully or correctly articulate it, and you probably don't understand. Once you tell them what their problem is, and they believe you understand and care about it, they will be willing to listen to what your problem is. Then you can negotiate. I can hear your thoughts right now. You're thinking "What the hell? I already said, over and over again, that I also want to hire as many Americans as I can! I already said I would prefer to hire Americans!" But that is proposing a solution. It is not articulating your understanding of their problem. If you do not first articulate your understanding of their problem, they will not believe your solution, because they will not trust you. You could be just making mouth noises to shut them up. It is only when you can articulate their problem, in your own words, that you show you understand it. Only then will they believe you care about it. Just tell them the problem they described to you, in your own words. Then tell them it's important, and you understand why they would be concerned. Seriously. Try it. It's like magic. You may be wondering why you to go first. Why do you have to show you understand and care, before they do? Simple. Because you're the wealthiest man in the history of the planet, and you have every member of the incoming administration on speed dial. And they are a bunch of engineers who got fired 'cause they wouldn't take the covid shot, and haven't been able to find a job, since. So you can do a heck of a lot more damage to them by not caring about their problems, than they can do to you by the reverse. And isn't it right, that you should care about the public? And demonstrate that? After all, you are in position you're in, not just because of talent, but because other people, at least some of them, believed in you and were willing to take a chance on you? You made all this happen, but you couldn't have done it alone. Now, other people want to hear that you believe in them, and are willing to take a chance on them. Isn't that fair? Most of these guys are young. They've been shut out of the best opportunities, universities, and jobs, for all of their adult lives, by deliberate policies intended to do just that. So they supported your ideas for change. They want to know that the people they supported aren't going to write them off as damaged goods because of the very things they were denied. You haven't convinced them of this yet. You need to.

WHAT IS REACT DOING WITH SUSPENSE?! WTH*CK honestly idk all the details rn but I know preloading is important and you'll probably want to get good at it if you want to optimize data loading and provide a snappy UX while it happens Here's how it looks in future React Router v7

A historical day for CSS 😀🎉 If you write any components used and/or styled by others, you know how huge this is! background: if(style(--variant: success), var(--green)); Even if you don’t, this will allow things like: padding: if(var(--2xl), 1em, var(--xl) or var(--m), .5em); GitHub issue: github.com/w3c/csswg-draf…

@danmall Original is better. The alternate version is hectic, everything shouting and trying to get my attention. You can’t read that bold section or red text without having read the previous blocks first. So interesting take, but not for me

One of my newsletter readers was kind enough to send me some feedback! They mentioned that my emails are blocks of text that seemed “tiring to read.” So, they made some changes to “help readers hop thru the article much easier.” Do you agree? Original vs. new version.

Goosebumps.

@housecor @connect_js Love this - component composition seems to solve a number of problems, but I'm interested to hear your take on this slide from your deck, if you could share some thoughts?

Just presented “Creating Reusable Components…That Are Actually Reusable” at @connect_js. Here’s the slides! dropbox.com/scl/fi/vrtxhl4…

When an athlete is told to run at 85% they run faster than if they're told to run at 100%. It's called the 85% rule and here's why it works: Carl Lewis was a 9 time Olympic gold medalist who was known as a master finisher but a slow starter. He began races 2nd to last but usually ended up finishing first. It became known that he's wasn't performing at full throttle. He was going at 85% the whole time. Why 85%? When you have your best performances it's never when you're trying your hardest. Instead the task usually feels easy & effortless. Going at 85% is a mindset about relaxation & performing at a high level while being in flow. It's about pacing, form & finishing. At 85% you're not striving or straining by operating at the very limit of your ability. You have room to think, focus & adapt. Applying the 85% rule helps you balance intensity while being focused & relaxed. Here's a few example of how to do it: At work: Instead of going full throttle, take your time, release the pressure & focus. Put an emphasis on optimizing your systems & adopt a mentality of expending 85% of your mental energy towards a task. Your perception of energy is the biggest component to your productivity. In your diet: Instead of trying to be perfect aim to get 85% of your food choices right. This takes the pressure off of you and gets you away from an "all or nothing" mindset. You want to be adaptable to any situation and hitting 85% is enough to get your body in shape. In your workouts: Instead of going to failure for every exercise aim for 85% intensity so you can focus on good form & keep your body injury free. We have a rule to keep 1-2 reps in the tank when lifting and this fits perfectly into it. Keys to the 85% rule: 1) Relax 2) Focus on form 3) Set your mind to 85% intensity 4) Work just below your maximum threshold 5) Stop when you feel close to 100% of your mental/physical capacity Instead of putting the pressure by trying to go 100 aim for 85% instead. Doing so might help you unlock new levels of performance.

@elonmusk My first logo

@tautology0 I believe this is a known scam method used to build up fake reviews. Might be worth double check and report the order if so!

Random extra Amazon delivery today. I didn't order them, but I will take up that challenge and leave them in random strange places.

⏳Countdown is ON for my live presentation on #MicroFrontends discovery! Get ready to dive into this exciting world and discover how to safely deploy your #frontend !🌐💥 Be part of the action - see you there! conference.microfrontends.cloud/schedule #LivePresentation #WebDevMagic #innovation

Absolutely right from Prince Harry 👇 “Our country is judged globally by the state of our press and our Government – both of which are at rock bottom." “Democracy fails when your press fails to scrutinise and hold the Government accountable." telegraph.co.uk/royal-family/2…

Bye Bye Boris: youtube.com/watch?v=lKrLBP…

@Keithamus At the moment - we go down to Samsung browser v7.2 due to significant user numbers in South Africa. Marketing emails and banners are helping move those users onto more secure browsers. Next up chrome 70!

🚨 Web developers 🚨 <a> and <button> are often misused. They have different purposes. <a> is for navigating <button> is for actions This leads to 2 common mistakes: 1. Using anchors for actions. 2. Using buttons to navigate. 1/4 👇

@Keithamus Mine was also todo with state/api management. Allows devs to build while the sever API is still being built. Using the amazing MSW by @ApiMocking.

@ApiMocking MSW allowed us to move a large number of browser tests to where ‘unit testing’ usually sit. This faster feedback cycle has no doubt save time and money. Thanks 🙏

If MSW introduced dual licensing, requiring companies with more than 3 employees to pay for it for commercial use, how would that affect you?

Lately, I noticed I haven't been delegating well (or enough) as a leader. Here's what I decided to do instead💫 → kyt.tips/delegate-video #kytmanagertips

Golden hour in Jamaica is one of the most beautiful things I’ve seen. Prints available at photos.danmall.com/landscapes/ Canon EOS R 24mm @ 1/250, f/11, ISO 100 EF 24–70mm f/2.8L II USM

@jaffathecake I said /1#foo but now would expect /1 after re-reading. I would expect the location.Greg line to ever be executed as the page had already gone back.

If you navigate from /1 to /2 (different documents), then run this in one JS call: history.back(); location.href = "#foo"; Where would you expect to end up? (Don't tell me what browsers do, I already know that, I want to know what you'd expect)