Learn more in 1:22 minutes. https://lnkd.in/g-JZC7g5
MacMan, Inc.’s Post
More Relevant Posts
-
Is this a “NEAR MISS or an ACCIDENT”……? Let’s share knowledge in the comment section
To view or add a comment, sign in
-
Backend Developer in PHP , Laravel , Nodejs , APIs , C#.DotNetFrameWork , TypeScript , JavaScript , MySQL , SQL Server Management System and MongoDB with Mongoose Package to use Schema
I Just do Some Examples Please Check this:
To view or add a comment, sign in
-
-
Here's trouble.... at 26:12 into the True to The Core session, Andrew Russo steps up with some great questions. https://lnkd.in/ge-N-rWx
To view or add a comment, sign in
-
-
The recording of my talk "Inner Workings of Safepoints" (based on https://lnkd.in/e3RYwpE9) is out: https://lnkd.in/eDt7XWpZ
To view or add a comment, sign in
-
Reynolds frame work for a control volume can be applied to the disturbance in mind (🥹🥹🥹😐)
To view or add a comment, sign in
-
-
5x Dow & Founders Award Winner. Portfolio Manager. Publisher of The Lead-Lag Report. Host of the Lead-Lag Live Podcast. Over 1 Million Social Media Followers across X, YouTube, Instagram, Threads, Substack, and LinkedIn.
Is this small-cap rotation a good or bad sign? Let’s examine a few arguments. https://buff.ly/4bKDByE
To view or add a comment, sign in
-
-
I strongly believe that “the system as working” is the most important thing. Being able to observe and describe the system IS the job—otherwise you’ll never be able to operate or change it. Diagrams are one way to describe the system. They should *not* be treated as “documentation for how the system works”. It’s a map. Not the territory. Only the system tells you how it is actually working (or not), not the diagram. Draw maps often, be practiced enough to be able to do it quickly. And delete them, often. Because maps are always wrong.
"Can somebody please just draw a picture of it?" -- Here's my thoughts on why you should take the time to draw your system regularly.
To view or add a comment, sign in