Trying to use Telus mycare for the first time @TELUSHealth can't book an appointment because the form is not submitted... send button broken? or the app itself?
1
97
Mauricio Mercado retweeted
[Corrected version]
We set out to explore the state of SSR performance across today's most popular libraries.
Let’s unpack the results and the corrections from our last version.
Mauricio Mercado retweeted
If more developers ran Linux on their desktop, maybe they wouldn't be so petrified of running a server by themselves. We are unlearning the basics of the Internet at an alarming rate.
Mauricio Mercado retweeted
TypeScript has such a weird beginning, like most software.
Proud of this section of the book:
Mauricio Mercado retweeted
Colombia🇨🇴 vs 🇦🇷Argentina
What is this
This is a disgrace!!!
#Argentina #Colombia #usa #trump #CopaAmerica #messi #usa
Mauricio Mercado retweeted
IF YOU DONT Have A TICKET!!! Stay HOME OR GO TO A BAR OR WATCH IT ON YOUR PHONE. !! Don’t ruin the game for everyone else by delaying the game because you guys are just freeloaders piece of shit fuck these fans #CopaAmerica
Scary Scenes in Miami, as the gates are breached at Hard Rock Stadium for Sunday night's Argentina-Colombia Copa America final. Truly hoping this situation is safely resolved before kickoff. [Via @the_bonnfire]
Reposting this as it is still relevant today. Plus people can always ise either node-tap or the builtin test runner with nodejs 20
If you're using vitest to test code that runs outside of the vite runtime, ala in regular Node.js, you've just created a test / prod difference that will result in bugs down the line.
This was the major flaw with using jest on Node.js code and people are just repeating it again.
41
Mauricio Mercado retweeted
this is very exciting
What a fucking joke I just got from @amazon just waited the entire day in my apt waiting for a @Sonos subwoofer and literally received an empty box with @amazonprimenow
1
2
128
Mauricio Mercado retweeted
I am so happy this is being implemented.
If every tab being named `page` in Next.js/Sveltekit folder based routing makes you go loopy, this new VS Code feature is going to be a life saver!
I repeat mocks are bad! cs-syd.eu/posts/2021-10-22-w…
When I was a Junior Developer, I desperately wanted to become Senior.
I imagined they’re abstraction wizards who write elegant code all day long.
Little did I know that an actual job of a Senior Engineer is educating others that mocks are bad, telling people to stay on the subject during countless meetings, and restarting CI ten times per day to find out why tests are flaky 😮💨
1
25
Mauricio Mercado retweeted
cost of bootstrapping your saas-
@vercel for deployment - $0/month
@neondatabase for db- $0/month
@clerk auth - $0/month
@axiomhq for logging - $0/month
@upstash for redis and kafka- $0/month
@resend for emails- $0/month
total cost- $0/month
In case your saas takes off and starts making $$-
vercel - $20/month
neon - $19/month
clerk auth - $25/month
axiom - $25/month
stash - ~$10/month
resend - $20/month
total cost- ~$120/month
$120/month is not bad for 1-3 person team IMO. instead of rolling out a solution for everything on AWS.
#buildinpublic #indiehackers #SaaS
Mauricio Mercado retweeted
Today I learned that node's EventEmitter suffers from an issue called "producer interference".
That's where an error thrown by a synchronous consumer (whomever called `on`) prevents the producer (the `EventEmitter`) from notifying subsequent other consumers.
This is something we had to change about Observable/Subject in RxJS 6 because of discussion about it in the original TC39 proposal and issues we saw it cause in production apps.
Imagine that you hand this emitter instance to several components, and each of those components is managed by a different team. An error from one of those components will arbitrarily stop some of the other components from getting notified and therefor they'll seem broken, even if they didn't have a problem. "Spooky action at a distance" sort of errors. These can be very hard to suss out.
(thanks @matteocollina and @dailydotdev for bringing this to my attention! very interesting!)




























