More

beginrescueend · on July 15, 2021

Yeah, when I saw it was a Software-Defined Instruction set, I immediately thought of Transmeta, as well.

beginrescueend · on Sept 2, 2020

Inside a company, I like transfer.sh, which is like an open source version of file.io - * https://github.com/dutchcoders/transfer.sh

That's good for the 5G +/- file transfer.

beginrescueend · on Dec 26, 2019

One week out of two, for a company size of 20.

beginrescueend · on Feb 5, 2019

The Bible, definitely. Pilgrim's Progress, by John Bunyan.

Those are the two most published books in history and have changed more people's thinking than any two other books.

beginrescueend · on Oct 13, 2017

Very cool idea!

beginrescueend · on Sept 2, 2016

Start with the book of Proverbs, follow its wisdom and advice, if all you're after is career improvements. Great wisdom.

(Wisdom about people, situations, attitudes, and actions are all found there).

But, move on to John, if you are eager for more.

beginrescueend · on Sept 2, 2016

0 points?!?!?

I thought this was about what non-technical books have helped me, professionally.

Intolerance?

beginrescueend · on Aug 29, 2016

I essentially have the same questions as you do. I'd like to evaluate Cloud Foundry, here, where I work.

I'll probably bake-off DC/OS and Cloud Foundry; maybe I'll also bake-off one or more of DEIS Workflow, SuperGiant, and maybe Apcera.

All of this is an eval for an enterprise-grade Docker platform, for development through production, including CI/CD.

beginrescueend · on June 15, 2016

I second Elixir. Concurrency and HA are the future!

beginrescueend · on Aug 28, 2015

Way to go! Great work, team.

beginrescueend · on July 19, 2015

It depends on what you mean, what your goals are, what you are trying to build, etc.

"No maintenance whatsoever?" I doubt it. Things break, get old, go obsolete, are insecure, and wear out.

Perhaps, you should worry about "nines of uptime" or "fixed requirements" or something along those lines.

Simplicity is first. The more complex, the more maintenance. "Everything Should Be Made as Simple as Possible, But Not Simpler" - http://quoteinvestigator.com/2011/05/13/einstein-simple/

"No moving parts."

Make it highly available and redundant. Power, cooling, networking, hardware, and software redundancies are needed.

Make it immutable. Change and mutable state will create maintenance. Implement functional programming, if you write software.

Monitor it and make it self-restart. Somebody already mentioned watchdogs, for hardware.

Make it ultra secure. No outside networking?

Program finite state machines....

If you imply a "hardware and software" solution, these points sound like you need redundant hardware and Erlang/OTP. Take a peek at OTP and the Erlang-based languages (Erlang, Elixir, Joxa, and LFE).

At least with redundant power, cooling, hardware, and Erlang/OTP (Elixir/OTP, etc.,) you gain the ability to do all of these things.

With Erlang/OTP, you can achieve very high uptimes, and if you design it correctly, you do have the ability to hot-patch running code, if you do have to (rarely) perform maintenance.

While you're at it, you also get distributed programming, concurrency, and parallelism, for free, with Erlang/OTP. This, in and of itself, can "reduce maintenance."

See https://pragprog.com/articles/erlang and http://stackoverflow.com/questions/8426897/erlangs-99-999999...