The data only contains the start and end station for each trip, but does not contain the full path. Route geometries are computed for each (start station, end station) pair using the shortest path from OSRM.
This means that the computed routes are directionally correct but inexact. Trips that start and end at the same station are filtered out since the route geometry is ambiguous.
This limitation comes with more interesting implications: e.g., I noticed that some bike trips are noticeably slower than average. For those I’d assume that the rider either took a detour or made a stop in between. The animation, however, makes it appear as if it was a very slow ride. Maybe worth considering to filter out all rides that are essentially walking speed or slower.
It also would be interesting to learn how many rides had been excluded altogether, just to put things into perspective.
Did Fischer ever make it outside of Germany? My father would bring us kits every time he would travel there for work in the late 80s/early 90s. The focus was more on Engineering themes, so not quite the same as a Lego or Playmobil set. More like Lego Technic for the most part.
The gaming laptops that have been made a bit less game-y without the RGBs and thick chassis turned out to be the sweet spot for me. Some compromises here and there, sure, but they mostly have the hardware I want. Asus has a good line up that works very well with Linux from 13 to 16 inches, all with dGPUs, AMD CPU (though Intel is also there), high-refresh rate OLEDs etc.
> fire mid-management and PMs to prevent the same thing from happening again
Firing PMs and mid-management would not prevent any of code reds you may have read about from Google or OAI lately. This is a very naive perspective of how decision making is done at the scale of those two companies. I'm sorry you had bad experiences working with people in those positions and I wish you have the opportunity to collab with great ones in the future.
Yeah the reflexive anti-PM anti-management stance posted above is typical here and of devs in general.
In theory, some engineers think they are perfectly capable of doing all the PMs work and all their own.
If they’ve never worked with a truly good PM, that’s a shame, they’d likely get more work done in a more timely fashion. I’ve worked with around 10 different PMs, the best kept stuff on track and aided with collaboration, reqs management, soft skills, handling tough customers, etc. they free up devs to do more dev work and less other work.
For something portable with a dGPU, I recommend the Asus ProArt px13. Works very well with Linux, including NixOS with the right config, with the community asusctl and supergfxctl. AMD, OLED screen, nVidia 4070 (4060 in the US, maybe we'll get 50xx next year). Downsides: the keyboard is not amazing, it comes with MediaTek WiFi, but is replaceable, and the SSD is 2230, which limits capacity. I haven't been able to fine-tune touchpad sensitivity in Wayland and I do get some screen flickering despite fiddling with some boot params and being on 6.17.x. Fewer constraints if you're willing to go 14-inch with the Zephyrus.
I tried some scanning on a Plustek 8300, which is supposed to be the fastest. The process is still extremely manual/slow and I don't think it's practical on a large scale. Many families who owned cameras in the 60s-70s-80s-90s will have potentially thousands of negatives to scan, but I don't see a solution that will automate that digitalization process.
Software could also use some improvement. Automating batch correction and clean up should be easier, IMO.
This really isn’t my area but it sounds like nothing is fast. DSLR may be fastest without just flat out hiring someone else to do it. But even with thousands of shots that would still take quite a lot of time.
And yeah, workflow is the thing that seems the worst. That seems like a great place to try to improve things to get a sale.
They don't need to "work" on Wayland support at all, all that work is being done by the FreeRDP project.
Also, sdl3-freerdp is the new Wayland client for FreeRDP is already available, and it works fine. You can just edit the shortcuts/bash scripts and replace xfreerdp with sdl3-freerdp and bam, you've got Wayland support.
PowerToys is not installed by default and neither is this Google app, obviously. It's absolutely reasonable that Google picks the most intuitive and common shortcut for an app launcher and if the user wants to maintain two or more launchers, it's up to them to configure non-conflicting keyboard shortcuts that are the most intuitive to them.
Problem with them, for the most part, will be about rebuilding the batteries and dealing with the poor quality of old screens.