Probably, which is unfortunate. I have personally seen a VP be shocked that morale tanked after a large layoff. I think he said “you would think they would be happy they still have jobs”. Lots of sociopaths in the C-Suite.
It’s just the beginning is my guess. If BYD or CATL commits to a factory /assembly in Canada I would expect limits to be raised on this as progress is made. Or if this goes well we could see limits raised as China drops Canadian product tariffs further.
My gut reaction is there is no way China is setting up vehicle manufacturing or assembly in Canada because the American President would go absolutely nuts. Canada is increasing ties and joint ventures with Canada but manufacturing would be a bridge too far for our little man in the White House.
It is getting to the point where lots of countries will stop caring how the US feels about things.
Between threatening, and some actual military intervention, with Iran, Venezuela, Greenland, Canada, Denmark, Mexico, and itself the US is spread pretty thin at the moment. I think Canada will slowly open up to China and boil the frog if you will.
If they are smart about it then it will probably work out really well for them. They will need a new market for their oil, timber, ..etc since the US is no longer a reliable partner. This will take years but as long as China doesn’t do something dumb like invade Taiwan they can just sit back and win while the US is busy self destructing.
I say this as an American, also a veteran, who loves his country but hates what is currently going on.
It isn’t free but 1Blocker works well across iOS and macOS devices for ad blocking. I am not affiliated with them; just have had it for the last 3 years.
They kind of spoke to it. Rebasing to bring in changes from main to a feature branch which is a bit longer running keeps all your changes together.
All the commits for your feature get popped on top the commits you brought in from main. When you are putting together your PR you can more easily squash your commits together and fix up your commit history before putting it out for review.
It is a preference thing for sure but I fall into the atomic, self contained, commits camp and rebase workflows make that much cleaner in my opinion. I have worked with both on large teams and I like rebase more but each have their own tradeoffs
Yes but specifically with a rebase merge the commits aren’t interleaved with the commits brought in from mainline like they are with a merge commit.
EDIT: I may have read more into GPs post but on teams that I have been on that used merge commits we did this flow as well where we merged from main before a PR. Resolving conflicts in the feature branch. So that workflow isn’t unique to using rebase.
But using rebase to do this lets you later more easily rewrite history to cleanup the commits for the feature development.
You'll still get interleaved commits. If I work on a branch for a week, committing daily and merging daily from main, when I merge to main, git log will show one commit of mine, then 3 from someone else, then another of mine, etc. The real history of the main branch is that all my commits went in at the same time, after seven days, even if some of them were much older. Rebase tells the real story in this case, merge does not.
I think it is more the point that the users for his job were external developers. The role is inherently user facing and user focused. I don’t think anyone was trying to say he wasn’t a developer just that his job wasn’t to directly develop products
Yeah, I guess I just wanted to add that because of the way that quote was cut at the end, made me believe that the person quoting me thought Osmani "isn't a developer".
Here is how I think of it. When I am actively developing a feature I commit a lot. I like the granularity at that stage and typically it is for an audience of 1 (me). I push these commits up in my feature branch as a sort of backup. At this stage it is really just whatever works for your process.
When I am ready to make my PR I delete my remote feature branch and then squash the commits. I can use all my granular commit comments to write a nice verbose comment for that squashed commit. Rarely I will have more than one commit if a user story was bigger than it should be. Usually this happens when more necessary work is discovered. At this stage each larger squashed commit is a fully complete change.
The audience for these commits is everyone who comes after me to look at this code. They aren’t interested in seeing it took me 10 commits to fix a test that only fails in a GitHub action runner. They want the final change with a descriptive commit description. Also if they need to port this change to an earlier release as a hotfix they know there is a single commit to cherry pick to bring in that change. They don’t need to go through that dev commit history to track it all down.
As someone who has set this up while not being a DBA or sysadmin.
Replication and backups really aren’t that difficult to setup properly with something like Postgres. You can also expose metrics around this to setup alerting if replication lag goes beyond a threshold you set or a backup didn’t complete. You do need to periodically test your backups but that is also good practice.
I am not saying something like RDS doesn’t have value but you are paying a huge premium for it. Once you get to more steady state owning your database totally makes sense. A cluster of $10-20 VPSes with NVMe drives can get really good performance and will take you a lot farther than you might expect.
I think the pricing of the big three is absurd, so I'm on your side in principle. However, it's the steady state that worries me. When the box has been running for 4 years and nobody who works there has any (recent) experience operating postgres anymore. That shit makes me nervous.
More than that, it's easier than it ever was to setup but we live in the post-truth world where nobody wants to own their shit (both figuratively and concretely) ...
datasette and datasette-lite (WASM w/pyodide) are web UIs for SQLite with sqlite-utils.
For read only applications, it's possible to host datasette-lite and the SQLite database as static files on a redundant CDN. Datasette-lite + URL redirect API + litestream would probably work well, maybe with read-write; though also electric-sql has a sync engine (with optional partial replication) too, and there's PGlite (Postgres in WebAssembly)
Hopefully this was some bug and not a sign of Apple starting to go down a user hostile path. I have Apple everything (iPhone, MacBook, iPad, home pods, the works) so not someone who dislikes the company. Just left a really bad impression.
Can’t edit so self reply. Nope this was intentional and it looks like I am about 5-6days late on this one. I didn’t see another post on this here though so hopefully this helps someone.
So just a crappy move from them then. Going to look hard at other options for all future purchases. Hopefully we get a reversal on this customer hostile stuff.
It isn’t an apples to apples comparison. But, you trade some additional operational overhead for a whole lot more hardware.
reply