jamesvandyne
People getting paid to charge their cars because the grid has a surplus of (probably green) energy.
The practical solution is to reallocate usage of the street to prioritize all modes of transport. i.e. Take a car lane and replace it with proper 2-way concrete barriered bike lane.
They're on the sidewalks because they don't feel safe riding in the street, and who would with huge trucks blowing past you at high rates of speed. But if you give them some infrastructure and someplace safe to ride, they won't be forced to dive through pedestrians on the sidewalk.
My son, who rides in a seat on the back, has a rain cover that provides shade when it's not raining and that we can zip an enclosure onto when it is to keep him completely dry.
If it's a heavy rain and we can't wait it out we'll take the car. But we mostly use our e-bikes as it's easier/quicker/more fun.
The way they handle the issue is "daikou taxi", which is a service from the taxi providers. If you've been drinking, you call them, they send a taxi with 2 drivers. You get in the taxi, and the other driver drives your car home.
Introducing a service like this would help reduce DUIs, I think. Having stricter laws about also helps avoid people making the decision to drive somewhere, where they know they're going to drink, in the first place. Instead they may opt to take a cab, find a designated driver etc, drink closer to home etc..
Technical monitoring is one solution. Making you calculate if driving is potentially worth, at a minimum 3-months of no driving, quickly makes you decide it's not worth the risk is another. That said, you'd think potentially running someone over would be enough risk for to avoid driving under the influence, but it's obviously not.
Blogs that aren't SEO fluff to get adsense money just don't appear in the search results. Discovery is the real issue. Finding these blogs independently or outside is nigh impossible.
I've been thinking it might be fun to make a GeoCities-esque neighborhood directory site that you could add your blog to help with discovery. But could you (I) change my habits to stumble upon sites in the neighborhoods instead of opening HN/Twitter?
There's still a bit of faff required to get setup (even with Wordpress), so I've been building what I hope will be a faff-free blogging engine ( http://tanzawa.blog ). It's finally gotten feature-complete enough for me to move my own blog it last week ( https://jamesvandyne.com ).
Implementation is pretty simple, too. I documented how I handled processing and display of webmentions on http://tanzawa.blog (a system I'm developing designed to make using the IndieWeb easier/less fiddly).
It's all simple enough to get setup using the IndieWeb Wordpress plugin.
macOS works much better if you manage windows with hiding, rather than minimizing. Once you get the hang of it, with cmd-h (hide), cmd-tab (switch applications), and cmd-‘ (iterate windows of an application) I (almost) never leave the keyboard and can get right to the window I need quickly.
When Rams speaks about design, it always makes me reflect on modern software and how we’ve regressed so much. Though I think’s mostly as a single widget does 20 different things, which isn’t a great idea in the first place.
https://github.com/uiur/remote-in-japan/blob/master/README.e...
I’m optimistic it will change, but probably not for another long while.
While the majority of large companies have this old style thinking, I think it will continue to change as the younger people get into positions to effect change.
Yes - more screenshots / a properly filled out marketing site are on the list of things to do. Good idea about an "About" section. Workshop is the name of our blog where we show / discuss Kwoosh as we build it.
Good point though, we could update the footer on workshop to be a bit more specific.
What's the killer is all of the work _surrounding_ that small task.
Actually charging sales tax didn't long. More or less
if address.region in TAXABLE_REGIONS: subscription.sync()
What took the longest was developing and deciding how the screens surrounding will work. Answering things like:
- Which fields do we want to capture for an address? - How do we want to store states (or provinces, or prefectures) in a standardized way? - Is there a library that will let me select countries and prefectures? (Answer yes, pycountry is pretty great) - How do I integrate this library into my backend / front end?
In my mind it's just fit and finish. Like making the motherboard and inside of the case as beautiful as the outside. If I try and half-ass it or skip it, I'm just going to have to double back and make it right.
I do appreciate your final sentence. I'll keep that in mind going forward. :-)
I'd to love to hear more about how you identified UX issues from pure logging data. Do y'all write anything up about this online anywhere?
We actually have soft delete in Kwoosh. We’re using Django on the backend. The way we went about implementing it was with a flag on our core data-type (Apps, Screens, Discussions, Tasks etc... all share a common parent class). Then we used an custom Manager class (Django’s name for the bit that lets you set default filters for models) that sets the default filter to only show active items.
If we want to query all objects including archived items (like for viewing them as read-only) we just change our code from Task.objects.filter() to Task.all_objects.filter().
We also have another flag for controlling visibility directly. This makes it manageable to remove a parent task, hide the children tasks, and restore into the expected states.
I should write a more in depth post on this for workshop. Maybe someone would find it helpful.
It let's you control things like temp, intercom to the kitchen and so forth. Automatic Bath one of my favorite things about living in Japan, even more so than the heated toilet seat.
2 of those working hours each day are blocked out for exercise, too, so this should be a real boon.