I once had a great presentation about this very topic!
The presenter gave us both the Tufte book and a detailed handout.
The idea is that you use the PowerPoint like you would an overhead projector, details that would otherwise be on slides are better as a handout that people can read/annotate as they want.
This was part of a summer REU and focused on academic talks, and this all falls apart in a remote setting - but I think there are ways to capture the essence of this style on Zoom.
Thanks for link. I've had hard time convincing my Swedish friends how same Temperature in Tokyo (RH around 80% now) is not comparable to the dry, windy Stockholm summer weather (even with record breaking temperatures a couple of years ago that momentarily put the temperature above Tokyo). I'll send this when they doubt it next time.
I would have thought this was more obvious to Swedish people, on account of experience with saunas. A 45°C Turkish sauna/steam room feels about comparable to a 80°C Finnish sauna (~10% humidity). And of course the way to make any Finnish-style sauna feel hotter is to pour some water over the rocks, increasing humidity.
You just need to them explain how sweat works. Sweat evaporate -> cool skin -> cools internal temp. Humidity high -> sweat no evaporate -> internal temp increases.
It's not really clear if this advice is for within the enterprise (a company that maintains so many systems they spend millions to integrate them) or at the edge (a company that needs to integrate with multiple third parties). I can see the argument for the intra-enterprise work being valuable, but at the edge I'm less convinced.
Good feedback. Most of the article is about integration inside an enterprise, although in the next installment I do talk about integration between organizations (hint: there are scenarios where I think low-code tools make sense there).
I arrived in my position in the late 90's, greeted by HP-UX, VAX VMS, and Unisys OS2200.
All of this was tied by our homegrown queue software.
Some years later, I was tasked with migrating HP-UX to Linux, in stages, and I was lucky enough to have found all the queueing source code, and I rebuilt it, imperfectly, on Linux. We hired back our past workers, including the original author, who made perfect my original port.
As the years have passed, I continued to improve this code, compiling with directives from "hardening-check" after bug hunts.
It has tied me to my role, but I suppose that I am happy here.
Minor nitpick: sign in with Google and Facebook don’t use SAML, they use OAuth and OpenID Connect. Leading with those as an example undermines the authors later points.
But at least Google can be used as a SAML idP for external services, which is what I think the author meant.
SAML as far as I know doesn't specify how exactly an identity provider authenticates a user but only how, once a user is authenticated, the user has a specific "identity" in the context of the service provider that initiated the authorization/authentication process. Therefore the authentication mechanism on Google/Facebook's side can be OAuth or something else, but once completed, the mechanism to convey the identity of the user to the originating service is SAML.
Mythical Man-Month isn't trying to say "surgical teams work well - let's apply that approach to software". Instead, it's an analogy to explore Fred Brook's thoughts on 10x programmers and "building systems with as few minds as possible". Brook's attributes the idea to Harlan Mill's paper "Chief programmer teams, principles, and procedures" - which I can't find online, but I'd be curious how Mills treats the analogy.
Funny. If you believe in bitcoin, then you would already have invested.
Otherwise what you (and many others, but not all) believe in as an investor is the possibility of a return from storing your dollars in bitcoin and retrieving the value later.
If you think this announcement would affect the price, look at price history data for the time of the announcement up to the date of going public. That could serve as some kind of signal given some model assumptions. Avoid confirming your own biases and establish your margin of risk as damage tolerance.
As I see it, betting on coinbase is betting on the volume of transactions increasing over time.
Normies will be buying their bitcoin on cash app, paypal, etc. In this way I feel CoinBase is a niche product with limited growth capabilities long term. The more CoinBase makes, the more the big names in tech/finance will expand their efforts to compete. CoinBase is a decent short to medium term play imo, whereas bitcoin itself is a longer term play.
The best way to get into Crypto from a traditional brokerage account is GBTC. It tracks mainly BTC and Ethereum. It is not a perfect match though, sometimes you pay a premium and sometimes you get a discount to the underlying cryptos. Currently it is at nearly a 18% discount where earlier in the year it was at a 10% premium (GBTC is currently 50.87, BTC is $59,515).
This is by no means a GREAT way to do it, just the best option currently if you are looking at crypto from a US based brokerage account.
Wow, I figured it always traded at a premium. 18% discount is huge, am I missing some downside of this arb opportunity (buy GBTC sell short BTC or BTC futures)?
GBTC has no redemption mechanism, you can wrap more BTC into GBTC but not the other way around. For ETFs this is what solves the arb.
You can do your arb but you still need to offload GBTC at some point and the only option is to another buyer of GBTC.
>The best way to get into Crypto from a traditional brokerage account is GBTC
So this is basically 100% speculation, because you can't even use the crypto you "purchase"? You're just hoping for prices to go up. How does that make sense for a purported currency? If people aren't using it, what is the value?
That isn't a very good argument. You might as well ask why do people invest in ETF's and mutual funds. The answer is because they view them as assets that will increase in value.
For me the most important aspect of decentralized assets is separation between money and state; challenging government monopoly power over money.
That said, there are conveniences and advantages to centralization. Centralized exchanges help supply and demand meet quickly and efficiently.
I think its possible for those systems to live together productively. There is freedom when I choose to trust and consent to other willing parties to take control of my assets. The problem arises when we are compelled to give up control by force of law.
I think you're pointing out the double-edged sword that is Docker; it's very easy to run and experiment with new technologies, even ones you might not be organizationally ready for. The "local" kafka that you used for a proof of concept is now AWS MSK in production.
The presenter gave us both the Tufte book and a detailed handout.
The idea is that you use the PowerPoint like you would an overhead projector, details that would otherwise be on slides are better as a handout that people can read/annotate as they want.
This was part of a summer REU and focused on academic talks, and this all falls apart in a remote setting - but I think there are ways to capture the essence of this style on Zoom.