Hey friends!
Whew, what a week. I hope yours was a good one, let's boogie!
Was this forwarded to you? You can subscribe here!
You should make a new programming language
Reckoning: How JavaScript broke U.S. Public Services
How I won $2,750 using JavaScript, AI, and a can of WD-40
The Nonvisual Website
This week I took my first Korean language class! For those that don't know, my husband is Korean and I've been wanting to learn the language (...beyond watching k-dramas) so I can speak more with my in-laws and teach our baby!
What's cool about this class is that the Korean Consulate here in Chicago offers it (and other courses) for a very low price, both online and in-person! They do this around the world (a friend of mine is taking one of their courses in Budapest as we speak) and it's such a neat way to share culture and educate the masses.
So far I'm still a bit of a noobie, but between overhearing conversations with family, watching shows, and now this class, hopefully I'll be up-to-speed in no time! 화이팅!
As DevOps teams adopt continuous deployment models, ensuring that software updates roll out smoothly as well as deliver new value to end users is crucial. Progressive deployment strategies provide a framework that helps ensure overall release stability and mitigates the risks often associated with large-scale deployments.
In this Amazon Web Services (AWS) webinar, AWS and DevOps Institute review some of the most efficient strategies for AWS environments with popular development lifecycle management tools from LaunchDarkly and CircleCI. See how they work with Amazon Q and Amazon Bedrock to maintain progressive deployments that meet high quality and operational standards and learn how to apply modern left-shift principles and generative AI-driven solutions to enhance application quality and security.
Last week, I had you return a list of unused variables! Awesome work Usman, Muhammad, Ricardo, Amine, Vasanth, Ashish, Tawseef, Sujeet, Neil, Ten, and Kriszti!
This week's question:
Given an array of function logs, where each log consists of a function name, a timestamp, and an event (either start
or end
), return the total execution time for each function. The timestamp is an integer representing milliseconds since the start of the program.
Example:
> calculateExecutionTimes([
{ name: "main", time: 0, event: "start" },
{ name: "subTask1", time: 5, event: "start" },
{ name: "subTask1", time: 10, event: "end" },
{ name: "subTask2", time: 15, event: "start" },
{ name: "subTask2", time: 20, event: "end" },
{ name: "main", time: 25, event: "end" }
])
> { main: 25, subTask1: 5, subTask2: 5 }
(you can submit your answers by replying to this email with a link to your solution, or share on LinkedIn, Twitter, Mastodon, or Bluesky)
Nintendo completely sat out the video game graphics wars. It’s winning anyway.
X-Ray Bauer Lite with PBTFans X-Ray
When Is “Recyclable” Not Really Recyclable? When the Plastics Industry Gets to Define What the Word Means.
What Adults Lost When Kids Stopped Playing in the Street
A Möbius strip is sobbing, and its friend asks, "what's wrong?"
It says, "where do I even begin??"
That's all for now, folks! Have a great week. Be safe, make good choices, and get your summer bucket list items crossed off!
Special thanks to IceSloth, Ezell, Sebastián, Ben, Kinetic Labs, Faisal, and Marta for supporting my Patreon and this newsletter!
cassidoo
website | blog | github | twitter | patreon | twitch | codepen | mastodon | bluesky