You might as well say that we should be paying per PR and Issue because, well, that part can’t just be free, you know?
5,668 karma · joined March 14, 2011
The Gigazone™, MN | Philadelphia, PA
Emailers, you can call me "swilson" at my work domain.
You might as well say that we should be paying per PR and Issue because, well, that part can’t just be free, you know?
The course I took on Literature of the Apocalypse, in fall of 1999, is probably one you would say is unnecessary. It has proven quite valuable as I learned how to read a lot, a lot more quickly. I learned how to write quickly as well. I also learned a lot about an important aspect of our cultural and political context, as western society is dominated by doomsday cults (especially the atheistic ones, everyone’s got a utopia they are trying to sell in order to get you to sacrifice your life for them).
Like most investments in yourself, you get out of it what you put into it.
We originally left GitLab for GitHub after being bit by a major outage that resulted in data loss. Our code was saved, but we lost everything else.
But that was almost 10 years ago at this point.
Indeed, this pattern, in particular, is extremely useful in environments where you are trying to making changes to one part of a system while multiple deploys are happening across the entire system, or where you are dealing with a change that requires a large number of clients to be updated where you don't have direct control of those clients or they operate in a loosely-connected fashion.
So, regardless of AWS RDS as your underlying database technology, plan to break these steps up into individual deployment steps. I have, in fact, done this with systems deployed over AWS RDS, but also with systems deployed to on-prem SQL Server and Oracle, to nosql systems (this is especially helpful in those environments), to IoT and mobile systems, to data warehouse and analysis pipelines, and on and on.
When I was developing server software for Windows, the first time I was able to setup a development environment by simply cloning a VM instead of spending a day-and-a-half with a lap full of MSDN CDs/DVDs, I never went back.
Prior to that, I was happily net-booting *BSD/Solaris servers all over my house/apartment.
Nowadays, we have so many tools to make this trivial. Your contention doesn't stand up to basic scrutiny of the available data.
If you are downloading software from untrusted sources (e.g. NPM, pip, and others) and running it on your primary working machine, or personal machine, then you are simply begging for trouble.
Do development, all of it, inside VMs or containers, either local or remote.
Use ephemeral credentials within said VMs, or use no credentials. For example, do all your git pulls on your laptop directly, or in a separate VM with a mounted volume that is then shared with the VM/containers where you are running dev tooling.
This has the added benefit of not only sandboxing your code, but also making your dev environments repeatable.
If you are using GitHub, use codespaces. If you are using gitlab, workspaces. If you are using neither, check out tools like UTM or Vagrant.
US leadership is undermined by the politicization of these grants. That is something that members of this community, largely a US-based, VC-oriented audience, should be deeply, deeply troubled by.
Netflix (the service) has an app named Netflix. You access Netflix via Netflix on... XYZ. Same goes for basically every other streaming service.
So Apple TV the service on Apple TV the app makes perfect sense if you are thinking about accessing their streaming service via other set tops where Apple TV the app is available.
My guess is that the Apple TV set top will be renamed to something else, perhaps "Apple Home".
Then it would be "Access Apple TV via the app on your Apple Home device" and the merging/conflation of "Apple TV subscription via the Apple TV app" will make perfect sense the same way you would say "Access Netflix via the app on your Apple Home device".
My guess is that "tvOS" will be renamed "homeOS" to go with it.
Agreed, though… MacOS isn’t a proper multi-user system and X is Not Unix…
Often times money will be raised at certain valuation and terms, but the cash is held in escrow (effectively) until milestones are hit.
The investors will do their due diligence on the feasibility. It’s a high stakes, high return game (if you succeed). Look around you… any physical device you see is basically funded the same way.
Yeah, he can give whatever title he wants to his subordinates, but the "CEO" of GitHub has been a mid-level VP for quite some time.
Because empathy is hard.
If you want to self-host a code forge... start here: https://forgejo.org/docs/latest/admin/upgrade