1,323 karma · joined August 26, 2019
Getting folks to quickly review PRs is difficult as doing so breaks the flow state of other people and results in constant thrashing and context switching between the work they are doing are reviewing PRs.
Even if the team is committed to quickly reviewing PRs, you are always going to have times when a bunch of people are in a meeting, while a couple are at lunch and a couple are knee deep in another issue and no one can look at your PRs for hours and you need to keep yourself unblocked.
Large PRs preserve the larger "1000 feet view" of what you are working on but are likely to be slower to get responses on and most likely less thorough thus a larger chance of things being missed.
Almost everyone I've worked with prefers smaller review so I just accept that trade-off of 1
PR1 -> PR2 -> PR3 -> PR4
The reviewer reviews and suggests a change in PR1, this change causes a merge conflict in PR2 and therefore in PR3 and PR4 as well. And then you have to go in manually resolve the exact same merge conflict all the way through you PR stack in each of the PRs. This gets annoying and hard to work with.
Does anyone have a better way of dealing with this pattern of merge conflict? I've tried using git rerere which in theory sounds helpful but doesn't seem to do anything when I strike this issue.
> Enabling HTTPS redirect means the fallback is no longer working, and if the browser doesn't let you in, you basically lost access to information even though it is still right there, just inaccessible.
This is the equivalent of saying that "since phantom issues with preflight checks on airplanes can sometimes result in cascading delays of flights on an entire airport therefore we should get rid of preflight checks on commercial airliners".
AppleTV like HBO is trying to follow a strategy of focusing on the quality of the product over quantity. It seems that most of their shows esp as of late get excellent reviews and look very expensive. It probably doesn't have the viewership of the bigger streaming services like Netflix/Max/Disney+ who have more populist content but they are managing to differentiate themselves from the other services.
They also need to give shows some kind of ending even if they are not part of their long term plans. Having a library of shows without ending is not attractive to customers.
AppleTV has been running circles around Netflix (and other streaming services when it comes to quality), what is the last critically acclaimed series on Netflix? I am not saying that your shows need to be critically acclaimed but you can't be in a state where your shows are getting panned criticlaly and on top of that not giving endings to your semi popular shows.
The recruiter spam is a small price to pay for the incredible professional value that LinkedIn provides for me.
That sounds like a "those people" problem. We don't hold people who use door knobs to account for the sake of a small number of people who like to lick door knobs and then get sick.
> I imagine it also cost a small fortune for Github to send this many emails.
That sounds like a problem for Github for not implementing any kind of checks and balances on their perfectly open feature if for some reason sending emails is expensive for them.
If he achieved "nothing" that would infact be preferable for Russia to the state they are in now. What he did is an equivalent of the manager of your team pulling a couple of all nighters over the weekend to do a "hero-refactor" on your codebase for "improvements" and then deploying it into production only for everyone to discover that the "improved" code has massive performance regressions, worse user experience and is harder to maintain... worse it can't be rolled back easily and the process of rolling it back will be slow and annoying, that is if the manager who made those changes even admits that it should be rolled back in the first place.
In 2021 streamers should be supporting atleast 1080p for Linux but if they can't I can live with 720p like Netflix does, but serving 480p is just disrespectful and looks awful on any decent size modern monitor.
What is abnormal is that in 2022 people think it is acceptable to be forced to use wireless headphones and have to constantly have to think and worry about keeping them charged, esp when they are used in a context where you quite possibly have them plugged in your ear all day.
Wireless headphones have their place (primarily in outdoor active settings in audio only contexts for small periods of time). But if you are sitting in front of your computer all day, there are these magical devices called wired headphones with infinite "battery life" and world class sound quality that you don't have to worry about being out of charge in the middle of an important meeting. Unlike wireless ones they also guarantee audio always being insync with video if you are watching a video regardless of the type of device/machine/operating system you are using them on, something I have never been able to get consistently working to my satisfaction with bluetooth headphones.
I recently got an old refurbished Thinkpad T430 for casual use when I am not near my desktop and installed Debian + LXDE on it. T430s are models from 10 years ago and is more enjoyable to work on than the 2019 MacBook Pro provided by my employer that I have to use for work. The only way I can make the MacBook tolerable is by using it in clamshell mode connected to monitors + physical keyboard/mouse so I don't have to interact with the actual hardware. It takes off like a rocket engine and warms my side desk pretty well (not to mention physically hot to touch, can't even imagine using it on my "lap"), docker is crap on it, not to mention the cmd-ctrl nonsense in addition to the things mentioned earlier. I have already dropped my Thinkpad a couple of times in pretty bad falls as it has survived whereas I don't have the same level of confidence in the MacBook.
For example I used to get a lot of pushback from the go community when using an assertion library, for those not familiar, go's testing library doesn't have support for asserts so you end up writing a lot of code like
if want != got {
t.Fatalf(....)
}
this gets esp annoying as you deal with more complex objects. Many in the go community criticize using an assertion library to write simple assertions as in other languages for your tests, citing that the go team members are against casually bringing dependencies in your project. Not realizing the intent Go Team's "statement against dependencies" is a targeted word of caution urging people to think about the dependencies they bring into their project rather than a blanket attitude against dependencies.Almost certainly Go Team would not advise against bringing in a build time time dependency that is not even gonna be part of the binary you ship that will make your tests easier to write and error messages consistent.
And now, just a few years later- Rust, Go are two of the hottest languages around, TypeScript is eating JavaScript, Python/Ruby have added static typing constructs, C# continues to do well in its niche and even Java of all languages has become somewhat cool again even though being Oracle product.
It's been an amazing transition to watch in action play out in front of my career, I can't even imagine those who have been in the industry for 30-40years who have probably been through a dozen of these cycles.
I am not sure if you are committed to the later but for the former you can do that in Java by the finding the right company. I also think (but don't have anything to back it up other than anecdotes) that the job market for the former is much bigger than if you solely restrict yourself to embedded systems, not just in Java but also in Rust/Go where a lot of companies are making that type of software.
For embedded device playing around, you could do some fun projects with micro-controllers (eg Raspberry Pico or ESP32):
* Write tiny db library (think sqlite with a smaller set of features)
* Write a multitasking OS for the Pico (easier than writing an os for traditional machines as you don't really have to support peripherals, you could look at FreeRTOS api and try to implement something that looks like it)