Fun read: To take humans back to the Moon, NASA has engineered a “fail-silent” architecture that handles everything from cosmic-ray bit flips to total processor divergence.
https://cacm.acm.org/news/how-nasa-built-artemis-iis-fault-tolerant-computer
Personal collective of ideas, thoughts and notes
Fun read: To take humans back to the Moon, NASA has engineered a “fail-silent” architecture that handles everything from cosmic-ray bit flips to total processor divergence.
https://cacm.acm.org/news/how-nasa-built-artemis-iis-fault-tolerant-computer
I recently came across a blog post that really resonated with me — it captures a philosophy I’ve believed in since I started building small companies and apps:
How I run multiple $10K MRR companies on a $20/month tech stack
The whole piece is worth reading, but the core idea is simple: keeping costs near zero gives you the same runway as raising a million dollars with a massive burn rate … but without the stress, the complexity, or the board breathing down your neck.
The one place I differ is on the database. I’m still firmly in the camp of running a managed Postgres instance, decoupled from the rest of the stack, rather than going all-in on SQLite.
Another cyclical pattern of my like back into photography. My Dad and sister inspired me along time ago to get into the hobby and its always more meaningful when you have a subject or interest which draws you in. In this cycle, it’s the girls Volleyball and sporting events/matches which have me intrigued along with capturing some shots for their social media accounts. I quickly learned shooting VB indoors requires a really good low light lens and the 70-200 2.8 seemed like a good choice. I have not shot video with it yet but hopefully soon (which was my primary motivation for the T2i years ago).
Nice comparison between the lens speeds for similar shots/situations:
I have had an app idea on my mind for a little while now with this premise: Thanks to laws like GDPR, tech companies are required to provide the ability for their users to download their data. In an effort to ensure I “own” anything I have uploaded to social media, I periodically download my data from platforms such as Instagram and Facebook. The issue with the platforms is that they do not have a standard data format, images properties such as location, their description or even dates they were taken, are not particularly easy to save or import into your local file system. Below is an example of a Instagram export and how the filesystem is structured 🙁
After building the open Source Reach SDK project, I realized it would be great to have an accompanying UI /Dashboard/Work bench where I would be able to test various notification methods and configurations before including them in my projects. Due to this, I build Reach UI, under the hood it is a simple static site with a Node.JS backend, using the Reach SDK. I think it does an ice job at showing how simple it can be to implement the SDK in your code base, and even includes some example code to make it even easier.
Check it out on Github below:


It definately, doesn’t feel like this at times 🙁

I recently got an Apple Vision Pro from work since we are currently doing some POC’s and innovation using the device. Overall, I am really impressed with the device. The eye tracking is definitively amazing and accurate, the experience is polished and the content is impressive. The “Guest” experience is solid (being able to turn it on, and pas the device to some else and get it setup).
There are a couple downsides, the weight is unbearable – I did a 30 minute fit at the Apple Store, and none of the cushions felt great for my narrow face. The other smaller downside, the app ecosystem just has not evolved sufficiently yet. The Apple Immersive Experiences are excellent, the Djay app is seriously awesome, but beyond that, we need to gain a bit more adoption before more killer consumer experiences emerge.


8 years ago I was introduced to Serverless functions on AWS. The concept of having the ability to run code, without worrying about running the underlying sever infrastructure was pretty appealing, not only from a management and operations perspective, but also from the associated 24/7 runtime costs.
Serverless computing enables you to focus on writing code, wiring it up to a API gateway or endpoint, and only paying when the code is executed. Some of the key functions or aspects which make this unique compared to a traditional server stack such as LEPP, MEAN, LAMP, etc. is that you have to consider the key underlying characteristics of a micro-service architecture:

A wonderful elaborate blog post by Amy Goodchild share what generative art is, including various methods, technologies, examples and theories.

A nice article on the science behind information/UI density along with some reasoning and justification for why great UI/UX is so important.
You must be logged in to post a comment.