Shout-outs to https://github.com/bbqsrc and https://github.com/cmyr for their quick, considerate, and effective responses to a couple GitHub issues I submitted for their respective Rust crates. Thanks!
We're finally seeing some of the cool promises of cyberpunk delivered: https://spectrum.ieee.org/tech-talk/consumer-electronics/gadgets/bosch-ar-smartglasses-tiny-eyeball-lasers.
Loving the cucumber-rust crate (https://github.com/bbqsrc/cucumber-rust). #Rust #Cucumber
Artist residency open call! Come do art with ThoughtWorks in New York City.
Serious question: How do the sizes of today's microservice code bases compares to the sizes of historical monoliths?
Are we building monolith-sized microservices without realizing it?
Remember that many of today's languages are far more compact and expressive than the ones in common use in the 90s and earlier.
Thinking of buying a PineBook to use as my primary social media device (to the exclusion of my phone): https://store.pine64.org/?product=11-6-pinebook.
More #Rust success today! Fixed an integer overflow bug.
When you're analyzing legacy code, try excising "lazy developer" from your vocabulary and see if you can find the true root causes. (Hint: Search for other systems that are offloading their own work onto the devs.)
As long as those root causes remain unaddressed, after all, then even the most studious of future developers may look as "lazy" as their predecessors.
Thinking of buying a PinePhone (https://store.pine64.org/?product=pinephone-braveheart-limited-edition-linux-smartphone-for-early-adaptor) with mobile web app development in mind.
wasmcloud: https://christine.website/blog/wasmcloud-progress-2019-12-08
This could herald the future of cloud computing.
Developer at ThoughtWorks.
Into Ruby, JavaScript, Rust, and many other languages.