1,692 karma · joined April 29, 2013
Follow me on Twitter @jetpack_john
Interestingly, If I ask it directly whether the JWST photographed an exoplanet, it says this:
> As of my knowledge cutoff in 2021, the James Webb Space Telescope has not yet been launched, so it has not yet taken any photos. However, once it is operational, it is expected to be capable of capturing images of exoplanets and studying their atmospheres. The James Webb Space Telescope is equipped with cutting-edge technology that will allow it to study distant celestial objects in greater detail than any previous telescope. This includes the ability to capture images of exoplanets, which are planets that orbit around stars other than our sun. The data gathered by the James Webb Space Telescope will help us better understand the conditions on these distant worlds and whether they might be capable of supporting life.
Dev Containers are basically Docker Containers (either pulled from a repo or built from a Dockerfile) with some additional metadata attached so they can work as a Development Environment. Metadata includes stuff to configure debuggers, IDEs, etc.
AS a very last resort, you might borrow from the Fed, but banks will generally avoid this as much as possible -- The Fed often charges a higher than market rate to discourage banks from using the discount window too much. Furthermore, borrowing from the Fed's discount window comes with a lot of stigma, since it implies you are unable to get funding from the market.
The most recent Odd Lots podcast episode has a great primer on the Fed Discount Window
> I was assuming that without a central bank account, reserves are moot
There are tons of ways to get reserves without a central bank account -- issuing stock, selling CDs or Bonds, selling liquid assets, etc.
> This is because the central bank determines reserve requirements for the commercial banks, so a bank without a fed account is limited in how much money they can 'create.'
FWIW, in the US the reserve requirements are currently 0%. They're also 0 in a lot of other countries (e.g., Canada)
But over time, as your reputation got better and you gathered more deposits, you would lend out far more than your reserves. You could do this as much as your risk tolerance allowed.
Historically, the Fed had a minimum reserve requirement of around 10%, meaning banks needed to have only 10% of the value of their deposits in safe, liquid assets. As of 2020, that requirement was dropped to... 0%
Loan -- an asset on the Bank's balance sheet. It's a promise that Bob will repay the bank a certain amount of money, plus interest
Deposit -- a liability on the Bank's balance sheet. It's an account that Bob can draw from at any time, and the Bank will promise to honor or pay the deposit.
These are created at the same time, and balance one another. The bank does not need the Fed to create the deposit at all, the create it out of thin air when issuing the loan.
When Bob comes to withdraw from his account, the Bank will pay him from it's *reserves*. The banks reserves are a pool of assets, cash, and deposits from other customers that the bank holds in excess of it's loans.
The bank can get these from a lot of places, not necessarily the Fed -- they could offer checking accounts to other customers, and hold some fraction of the assets in a customer's checking account in reserve. Banks offer all sorts of incentives to get people to deposit long term(CD, Savings Accounts, e.g.) for this reason, but they almost never have 100% of the money they are loaning out held in reserves. Their entire bet is that only a fraction of the deposits will be withdrawn at any time.
The Fed doesn't need to be present for any of this, but they provide an important stabilizing function, ensure liquidity, and can adjust the money supply through open market operations or banking regulations.
The problem comes if people try to withdraw or move their deposits, and the bank does not have reserves to cover the withdrawal. In these cases, the bank would need to sell some of it's assets -or- borrow money from somewhere else. If they can't liquidate assets fast enough, they have a liquidity crunch and will need to borrow or sell the company. If the value of the assets is below the amount being withdrawn, they're insolvent.
The Fed can act as a lender of last resort in liquidity times, but if a bank is insolvent they likely won't be able to post collateral to get loans from the Fed.
We’ve been working on a similar workflow with Devbox (https://jetpack.io/devbox), using Nix to install and run dev env services
You can read more about how it works here:
If it requires some migration, would love to see a guide on how to wrap a Nixpkgs project in a barebones NixOS config
I could reach out to you over email, or we could chat on our Discord server at discord.gg/jetpack-io
So your patient might be ok if you fire Ned, but if you try to make changes and a critical system goes down, it might take you a lot longer to fix things without the specialists in that system.
You could keep one specialist around for each system, but then you have a very small bus factor.
It also has some early functionality where you can turn that shell into a Docker container, so you can run the same shell + program in other environments or in the cloud
Fortunately, the API is programatic, so it’s possible to build abstractions on top to make dealing with those concepts easier. But that can also take a lot of work to build from scratch…
Deflation, with its disincentives to investment or economic growth, would reduce employment and real wages. Most Americans would lose their jobs or see their wages cut as the economy ground to a halt. Anyone with debt would likely be trapped working for the rest of their life at subsistence wages, never making enough to pay their debts off.
At that point, you'd need an entire overhaul of the economy, not just an algorithmic monetary system
I think it's hard to say that there's a causal relationship though -- a lot of companies that can afford to invest in automation are those with already successful products + money to invest. This may change as it because easier to automate provisioning and deploying to environments (something I'm working on at my new company, jetpack.io)
But I also think it’s going to be difficult, using the methods available feasible for this kind of study, to draw strong causative conclusions about how dev ops practices impact business performance. There’s a lot of confounding variables that are hard to control for.
So I think I share both your takeaways
I did find the capabilities and KPIs that Accelerate emphasizes useful, however. I agree with the author that there are a lot of other issues (such as building the wrong thing) that impact a businesses overall success. However if you’re on a team that’s focused on developer productivity, the four metrics offered (Deployment frequency, Lead time for Changes, Time to Restore Service, and Change Failure rate) are pretty good ones to focus on.
I also found surveys useful at identifying gaps in monitoring, detecting sources of toil among an engineering team, and gauging overall employee satisfaction, though they are not great at getting granular data. That said, they can provide good areas to dig in with more ethnographic research methods.
> Kubernetes is a platform for building platforms. It's a better place to start; not the endgame.
https://twitter.com/kelseyhightower/status/93525292372179353...
Everywhere I've worked, having developers use and develop Kubernetes directly has been really challenging -- there's a lot of extra concepts, config files, and infrastructure you have to manage to do something basic, so Infra teams spend a lot of resources developing frameworks to reduce developer workloads.
The benefits of Kubernetes for scalability and fault tolerance are definitely worth the cost for growing companies, but it requires a lot of effort, and it's easy to get wrong.
Shameless plug: I recently cofounded https://www.jetpack.io/ to try and build a better platform on Kubernetes. If you're interested in trying it out, you can sign up on our website or email us at `demo [at] jetpack.io`.