> The only real justification here is that it probably makes lives easier for Apple developers since they can now manage a single codebase for settings vs. separate ones.
While this is probably a large factor in their decision to do this, I wouldn't say that "no one expects a computer to work exactly the same way as a phone or tablet". My parents would definitely say otherwise. In fact, there's been some discussion on HN before about today's kids & teens not knowing how computer file systems work [0].
Obviously the majority of folks on this orange site have a strong understanding of how computers and filesystems work. However, there are more and more people that will grow up fully on tablet and mobile devices that will have a completely different mental model of what a "computer" is.
It sounds like you were a fantastic manager who cared about their team, I'm very sorry to hear that. Seems like it can be a very thankless job a lot of the time.
Hopefully we can normalize showing appreciation from all directions (direct reports, sr mgrs, directors, etc.) for those who deserve it.
Sounds like you had a great director who was willing to shield their org from bs top-down demands.
I didn't appreciate this skill until I had a manager who did the same for me. Having a manager who can ruthlessly prioritize, set expectations, and help navigate all of the corporate bureaucracy is a godsend.
Not to mention a nicer peripherals like the screen and keyboard. Majority of people are not purchasing a MBA for pro-grade workloads. I think the MBA meets the requirements for its niche quite nicely.
Your comment reminded me of this article[1] that has probably been posted plenty of times on HN. You've described both the "hacker" and the "mathematician" tribes.
> That's what I love about engineering generally, the ability to roughly understand what is going on around me down to some first principles.
This! It's very empowering and one of the things that drew me to tech/computers. Being able to understand things helped me realize the potential of what is possible with computers/computing technology.
I majored in EE in undergrad and didn't really appreciate my EE education until I got older (I was more interested in software).
I think the person you responded to was referring to Discourse[1] forums, not Discord[2]. Although I agree with you and the gp, both Discourse and Discord have very different incentives than traditional social media FB, IG, etc.
"If you owe the bank $100, that's your problem. If you owe the bank $100 million, that's the bank's problem."
Technically you're correct. If only a handful of employees migrated, they could probably be let go pretty easily. No skin off Facebook's back.
Now if hundreds or thousands of employees migrated, Facebook needs to make a decision whether enforcing the RTO or not will hurt them more. Regardless of technicalities, demanding a non-significant percentage of your workforce to uproot their lives is not an easy ask (or great look).
My experience is pretty similar to yours but I think what you need to try to understand is that everyone has a different level of what is an acceptable "minimal" lifestyle. For a lot of people, these are habits/behaviors that they grew up with as well. It's complicated.
Lack of financial literacy is another problem that, I think, exacerbates the above.
Could you share some of your experience with nbdev? I'm a huge fan of what the fastai team has been doing and I've tried nbdev, but I haven't been convinced yet. Particularly with the pull request experience, it's not very easy to do code reviews.
FWIW my team uses bitbucket and the PR experience is significantly worse than github/gitlab unfortunately.
I would love to see that as well, I'm wondering what has stopped them from integrating it already... Maybe there's room for some contributions from the community here :)
I've been using the VSCode Insider's release as well and have been loving it and the new native notebook features for all the reasons you've listed already.
That's an interesting solution. I believe this is similar to what Joel Grus does [0], except %s/jupyter/ipython.
Slightly tangent, but has anyone figured out a good solution for version controlling jupyter notebooks?
The closest thing that we've found has been to use the notebook percent format in a simple .py file [0][1]. It plays with git much nicer than an .ipynb and it is still interactive enough for rapid prototyping. However, it would be nice to have some first-class support from Jupyter on this.
This is similar to a resource that atlassian has put out on storing dotfiles [1]. It is also similar to what I use and I can vouch for this method as well.
For many people integrating batteries into their projects, this is true and you can simply take most off-the-shelf cells with the right voltage profile and put them into some series/parallel config.
At least with lithium-ion technologies, for larger applications, this ignores a lot of the degradation phenomena and electrochemistry of the battery.
would this mask any errors that would occur later in the validation?