iphone: https://apps.apple.com/de/app/nunav-navigation/id1193133974?...
android: https://play.google.com/store/apps/details?id=com.nunav.play
253 karma · joined September 4, 2013
Twitter: https://twitter.com/RomPic Email: hn at pickl dot eu Web: https://pickl.eu/
iphone: https://apps.apple.com/de/app/nunav-navigation/id1193133974?...
android: https://play.google.com/store/apps/details?id=com.nunav.play
Its predecessor was basically hacked together for a company retreat while stranded at schiphol airport for a whole day.
It has quite some usage, but basically only covers its hosting costs.
The query returned an extremely high number of results and when I discovered this I questioned my SQL-fu, my sanity and my trust in computers.
I found that we were hit by a bug that was fixed 6 years before I discovered it (https://sqlite.org/src/info/6f2222d550f5b0ee7ed). Sqlite's query planner assumed that a field with a not null constraint can never be null, which isn't the case for the right hand table in a left join.
I fixed it by adding a not null check in the query and then later by updating the library. After that the 1 hour query ran in ~700 ms.
The new "owner" will keep the bike as he has bought it in good faith. The shop will claim that it cannot check every used bike. The rightful owner could try to get money from the person who stole it (if found), but they most likely don't have any money.
It's the perfect crime and the reason why we cannot have nice bikes. People are literally sleeping with their expensive bikes in a room.
At the same time there have been roughly 60 release notes that mention performance since 3.8.6, so these came for free with the update: https://www.sqlite.org/changes.html
On a quiet day, I was able to save the temporary table used as part of the process and run the problematic query against it in an isolated fashion.
The query returned an extremely high number of results and when I discovered this I questioned my SQL-fu, my sanity and my trust in computers.
I found that we were hit by a bug that was fixed 6 years before I discovered it (https://sqlite.org/src/info/6f2222d550f5b0ee7ed). Sqlite's query planner assumed that a field with a not null constraint can never be null, which isn't the case for the right hand table in a left join.
I fixed it by adding a not null check in the query and then later by updating the library. After that the 1 hour query ran in ~700 ms.
This faster run time also helped with smaller projects and in the end allowed extending our test suite considerably.
Tldr: Keep your dependencies up to date.
I'm still using the old one during the week as it only takes a few minutes to swap.
The result is a share of 25.8% (short-term) to 39.3% (long-term) of all employed persons in Austria who could in principle work from home on a permanent or temporary basis.
By overestimating the work-related passenger kilometers, this results in a savings potential of about 300 kilotons of CO2 equivalents per year, if about a quarter of all employed persons in Austria work from home for 40 % of the working time (or 2 out of 5 working days).
Due to undesirable rebound effects, such as an increasing distance between home and work, induced traffic as a result of freed-up capacity, or increased capacities or increased leisure mobility, this potential can increase to 90 kilotons of CO2 equivalents per year.
From https://www.agora-verkehrswende.de/veroeffentlichungen/wende... For Germany:
The climate effects of home office were estimated for 40 percent of the workers, each with two home office days per week, were estimated to save 5.4 million metric tons of CO2 equivalent per year.
This corresponds to 18 percent of percent of the emissions from commuting to work or 4 percent of the of total passenger transport emissions (Büttner and Breitkreuz 2020).
There are a lot of similar 10 year old reports on the net. E.g.: https://www.badcaps.net/forum/showthread.php?t=24494&highlig...
Some background / video and context here: https://itrevolution.com/understanding-job-burnout-christina...
I even put https://www.nohello.com/2013/01/please-dont-say-just-hello-i... in my status.
I still think adding the name after the hi goes a long way.
disclaimer: I met the founder once at a party.
it provides the possibility to easily visualize internal informal networks. Especially simple using mobile phones.