Robert Nishihara’s Post

Because moving quickly (and safely) is a competitive advantage ;)

Surely adding new features will fix the problem.

I think my preference depends on if I am wearing glasses.

Surely adding new features will fix the problem.

I made a custom input function for a pause menu instead of making use of the engine's focus input system over at Godot. (Look at the console log)

Join Renesas and Crank for an exclusive webinar, where industry experts will delve into the essential elements of creating engaging and memorable embedded products. Understand the best practices for GUI development. June 20th:

Beta version is on the way...

Great presentation by Marko Matotan shedding light on our current bare metal setup, which aligns seamlessly with 37 Signals' recent transition to an equally captivating infrastructure, boasting the following key advantages:independence from Cloud Providers like Amazondrastically reduced costs (hardware expenses recouped within a month, solely through cost savings!)more nuanced control!If you're intrigued by our Bare Metal/Kubernetes/ArgoCD/Self-hosted GHA + Docker Registry setup, stay tuned for our blog series as we delve into the intricate details of our journey! Check it out here: https://lnkd.in/d5my9mE4 #kubernetes #baremetal #infrastructure #devops

𝗕𝗲𝘄𝗮𝗿𝗲 𝘁𝗵𝗲 𝗰𝘂𝘀𝘁𝗼𝗺 𝗾𝘂𝗲𝘂𝗲 My first opinion piece for Resonate HQ exploring the hidden costs of adopting a tech stack that forces you to use its own proprietary queueing solution https://lnkd.in/gGmjeD4x

Question 4: Promise Behavior console.log('Start'); Promise.resolve().then(() => console.log('Promise 1')); setTimeout(() => console.log('Timeout 1'), 0); Promise.resolve().then(() => console.log('Promise 2')); setTimeout(() => console.log('Timeout 2'), 0); console.log('End'); --------------- Answer: The order of output might vary, but possible output: Start, End, Promise 1, Promise 2, Timeout 1, Timeout 2. why ???