Tailscale Inc. is a software company with a freemium business model based in Toronto, Canada. It was founded in 2019 and is headquartered in Ontario. Tailscale provides an open-source software defined mesh virtual private network (mesh network VPN) software and a web-based management service.[a][1][2] The company provides a zero config mesh VPN service under the same name.... The open-source software acts in combination with the management service to establish peer-to-peer or relayed VPN communication with other clients using the Wireguard protocol. If the software fails to establish direct communication it falls back to using relays provided by the company. The IPv4 addresses given to clients are in the Carrier-grade NAT reserved space. This was chosen to avoid interference with existing networks. The configuration also allows routing of traffic to networks behind the client on some clients. https://en.wikipedia.org/wiki/Tailscale https://tailscale.com/ (more)

setting direction for a product and making sure it happens (more)

Livebook is a web application for writing interactive and collaborative code notebooks in Elixir... built with Phoenix LiveView. https://livebook.dev/ (more)

previously iPython (more)

Chris Granger project: (more)

creator of LightTable; https://chris-granger.com/ https://twitter.com/ibdknox

Text Editor/IDE. LightTable is an integrated development environment for software engineering developed by Chris Granger and Robert Attorri. It features real-time feedback allowing instant execution, debugging and access to documentation.[5] The instant feedback provides an unusual execution environment intended to help developing abstractions.[6] The development team attempted to create a program which shows the programmer what the effects of their additions are in real-time, rather than requiring them to work out the effects as they write the code.[7] Though the program began by only supporting Clojure, it has since aimed to support Python and JavaScript due to their popularity. http://en.wikipedia.org/wiki/Light_Table_(software) (more)

contra Imperative, as Computer Programming model (more)

Model-Based Design (MBD) is a mathematical and visual method of addressing problems associated with designing complex control,[1][2] signal processing[3] and communication systems. It is used in many motion control, industrial equipment, aerospace, and automotive applications.[4][5] Model-based design is a methodology applied in designing embedded software. https://en.wikipedia.org/wiki/Model-based_design (more)

Domain-driven design (DDD) is a major software design approach,[1] focusing on modelling software to match a domain according to input from that domain's experts.[2] Under domain-driven design, the structure and language of software code (class names, class methods, class variables) should match the business domain. For example, if a software processes loan applications, it might have classes like LoanApplication and Customer, and methods such as AcceptOffer and Withdraw. Criticisms of domain-driven design argue that developers must typically implement a great deal of isolation and encapsulation to maintain the model as a pure and helpful construct. While domain-driven design provides benefits such as maintainability, Microsoft recommends it only for complex domains where the model provides clear benefits in formulating a common understanding of the domain.[3] The term was coined by Eric Evans in his book of the same title published in 2003. https://en.wikipedia.org/wiki/Domain-driven_design (more)

alternative to Test Driven Development? (more)

repeating, cycling (more)

educational model (Network Of Learning) (more)

Like a retrospective, but triggered more by a specific "event", most often a production outage or important bug... which means there's a certain urgency to "fixing" it (Time to Restore Service as one of the Four Key Metrics), but you need to generate enough info during the fixing process to be able to agree afterwards (a) what was actually/fundamentally broken, (b) what correction actually fixed it, and (c) what that implies for preventing a recurrence. (more)

First principles thinking consists of deriving things to their fundamental proven axioms in the given arena, before reasoning up by asking which ones are relevant to the question at hand, then cross referencing conclusions based on chosen axioms and making sure conclusions don't violate any fundamental laws. https://en.m.wikipedia.org/wiki/First_principle (more)

Grad School/Certification for doctors (healthcare)

actually, you can never model/build a whole system, just the part of it that matters (more)

A root cause is an initiating cause of a causal chain which leads to an outcome or effect of interest. Commonly, root cause is used to describe the depth in the causal chain where an intervention could reasonably be implemented to change performance and prevent an undesirable outcome. The term root cause has been used in professional journals as early as 1905, but the lack of a widely accepted definition after all this time indicates that there are significantly different interpretations of exactly what constitutes a root cause. The two biggest differences in viewpoint regard the possibility of an outcome having more than one root cause. http://en.wikipedia.org/wiki/Root_cause (more)

A pre-mortem, or premortem, is a managerial strategy in which a project team imagines that a project or organization has failed, and then works backward to determine what potentially could lead to the failure of the project or organization.[1][2] The technique breaks possible groupthinking by facilitating a positive discussion on threats, increasing the likelihood the main threats are identified. https://en.wikipedia.org/wiki/Pre-mortem (more)

Martin Cagan on some guidelines for doing Product Management in an Agile Software Development process. Rapid cycling of ProtoTypes before the Iteration starts. As a product manager/owner, your main responsibility is to come up with useful and usable prototypes and user stories that your team can build from. Replace heavy PRDs and Functional Specs with ProtoTypes and User Story-s. (more)