mdtusz

I imagine Photoshop will be relatively quickly made available, and maybe even Ableton, but based on how most engineering software progresses and develops and how much slower engineers themselves are to use modern tools, I can't imagine any cad software will be ported for ARM within the decade.

RTK is great! The only thing I wish was a bit different is the `createAsyncThunk` function. It feels dirty providing the action-type string manually, when for all the other actions, this is essentially invisible.

A part of me is happy to see these types of tools introduced to python, but another part makes me wonder why people continue to use python when they see the value of things like `Option`/`Maybe`'s, `Result`'s, instead of just using a language with the features included from the start.

In my experience, the initial ease and speed of development when using python doesn't nearly outweigh the medium to long-term costs of maintaining it and developing the codebase further - at least for codebases that are more than a simple tool or something like a django app. Writing things like go, rust, scala, java etc. isn't that much more difficult or slower, but it does require more up front planning and understanding of your problem domain.

OSX only, but GitUp is the only GUI got tool I have used that feels like it actually is helpful for a git workflow. I _really_ wish it worked on Linux, but it's basically not possible without an entire rewrite.

https://github.com/git-up/GitUp

At risk of sounding like a gatekeeper, maybe someone getting reprimanded for using an untested, production unready library isn't a bad thing.

It's not realistic to read through all the source of every dependency you use, but it should be encouraged for developers to take a more active approach in evaluating dependencies they pull in - at least to check how active development is, what sort of open issues there may be, test coverage, code quality sniff tests, what the license is etc.

I'd be willing to bet most GPL violations are due to ignorance, rather than intentional.

I agree with what you've written, but this isn't an argument for stand-ups.

What you're advocating for is regular communication, and people being involved in each other's work. Stand-ups c_an_ help with this, but they aren't the only solution, and in my view, are one of the less effective solutions.

Open, unstructured conversion has always been a better way to solve problems and move things forwards in my experience, and stand-ups entirely kill that by having an orthogonal purpose in the eyes of the manager (unless they're in the trenches doing the same work everyone else is, which is rarely the case).

Let your developers have their own standups however they want to do them. Make sure they do meet and discuss, but stay out of it if you're not right there with them helping to solve the problems.

FWIW I have a t480s with the 1440p display and am using Linux and my battery life is typically around 6 hours or so for regular use. If I start running more dev tools and building things it plummets as to be expected, but the display really doesn't seem to make much difference.

The biggest thing I miss from my MacBook is being able to open it after a week of being closed and still have battery. There's definitely something not going into deep sleep when I close the lid, but that's probably my fault.

> Zoom has not and will not build a mechanism to decrypt live meetings for lawful intercept purposes.

That seems to include past tense.

ThinkPad speakers are terrible to the point of being basically unusable even in a quiet room for most video calls.

I can live without the trackpad (once you learn to love the trackpoint you'll never go back to a trackpad) but the speakers and display are the two lacking points. Even though it's a 1440p display, it just doesn't look as nice as a "retina" display and getting a 4k display on a 13" laptop is in my mind an absurd waste of battery and money.

I can't say that it's specifically the case, but in Montreal, there's been an ever increasing number of vacant commercial spaces - seemingly because they know that "eventually" some BigCo will come along and be willing to pay the extremely high rent. As anecdata, there's a corner space on the ground floor of Duluth and St. Laurent that's been vacant for well over a year - maybe even two. It's pricing out smaller businesses, and even though the space is available and empty, it's just unaffordable and priced far above the true market value.

We don't want more A&W's and Starbucks, but that's what eventually happens here. The only places that survive are bars.

I think a part that needs to be considered in the comparison is also the concept of safety factors.

Many structural engineering projects are built with a safety factor greater than 1, which allows for - as you'd imagine - safety. In software, it could absolutely be done that every function has explicit validation checks for each input, and that more safety, error handling, and checking is written. The economics just don't make that viable though except in the most extreme situations where this is required. In aerospace, with the exception of the recent Boeing debacle, there's been very few software related issues (that I know of) relative to the number of CPU cycles run and flights taken - I'd be willing to be there's far more mechanical issues that cause grounding and maintenance cycles.

Now look at civil engineering and infrastructure. How many roads do we drive over daily filled with potholes? How many bridges get patches and repairs every few years because of concrete cracking and rebar rusting? (I live in Quebec, so there may be bias in this statement). Maintenance like this is just paying down tech-debt - the same as in any field.

Software absolutely can be built to a high level of robustness (and it is) - it's just not economically sensible in most cases.

Just curious, what's your reasoning for thinking C wouldn't be a good fit? I'd think either would be fine choices given their ubiquity. (Not a C or Java programmer, just like to learn!)

Cargo works pretty well too.

You mean advil? Aspirin is most definitely not ibuprofen. Or is this just proving the point note that language does matter a lot.

A fantastic example of this _not_ happening in js libraries though is Plotly.js. It's still on a 1.x release and has maintained backwards compatibility (for the most part) with the original API for _years_.

Full disclosure, I used to work there (specifically, on plotly.js).

For what it's worth, this design has been vetted by health care professionals and provides better coverage, as well as being faster and easier to print.

https://github.com/aon3d/covid-face-shield

Full disclosure: I work for Aon3d.

Buffers.

They are not integrated.

That said, vim and emacs can be in a way a component of a DIY IDE - you just need to put the work in and build it yourself. I exclusively use vim with a handful of useful plugins, scripts, and additional CLI tools in other terminal splits.

The terminal is my IDE.

I think a lot of the fear of rebasing comes from not fully grokking what it does, and not rebasing often enough.

My workflow typically involves rebasing my local branches on master every time I switch a branch or start a work session, so typically conflicts that need to be resolved are very clear and small things (e.g. someone else adds a case to a switch statement in the same place your branch does).

The biggest benefit to this that I see is that your diffs are then much more clear in what they're doing, and you have the option to update the commit message to reflect the conflict resolution if required.

That said, if you have a big feature branch and try to rebase it after a month vacation, you're gonna have a bad time.

I'm not too sure if it has this built-in by default, but I've found kitty terminal to be the nearest thing to iterm for Linux. Lots of customizability and it has fairly good docs which is always a plus.

Correct me if I'm wrong, but the example given of a link with "cancer" in the scroll-to-text part wouldn't show up in a DNS query would it?

My understanding was that only the domain is queried, but the full path is not seen by a DNS server.

Minor nit, but tacking is by definition, turning into/across the wind.

As a counterpoint to this, jira is _not_ great in any environment precisely because it is so flexible and requires a team to manage it.

If a job needs to exist purely to maintain a third party tool that you pay for, you probably should find a new tool or make the tool yourself so that the employees work value is retained. It's the equivalent of doing a complete kitchen renovation on an apartment that you rent.

If you ever visit a city that gets substantial snowfall, road markings are essentially nonexistent, even when the snow and ice melts in the spring.

I'd argue that racket's ecosystem is ideal for getting young people interested. You can build gui tools and do graphics programming out of the box, very easily.

My go to language to refer people who want to learn is Processing though. Easy to use, and the documentation is fantastic (and Dan Shiffman is IMO the best programming educator out there for kids and adults alike, whether or not you like his high-energy style).

You should use an EDK (despite the name sounding scary) if you're anywhere with cracks or areas that a double fisherman's will get caught. The EDK is asymmetric so it's less likely to get stuck, and is generally faster to tie (and untie). Fears of it rolling out are a bit overstated - just leave a solid 6 inches of tail or more.

Could be a hardware product. Shipping hardware early is a nightmare.

I'm not sure if there's a non GUI interface for it, but zathura does this for pdfs.

On any plane I've been on, the armrest barely reaches my shoulder when in the up position. I have no idea how you can manage this.

Boilerplate may not be the best term. It's more the presence of fitting into types and structures that certain libraries/frameworks provide where you just need to be much more explicit than in some languages. It's definitely a good thing long term though.

Writing code without dependencies/frameworks that have a required structure is a joy, however.