1,097 karma · joined May 5, 2014
mansib [at] radish.coop
Personally, my process after this is to express my thoughts in bullet points, followed by inserting any placeholders and captions for any graphics (e.g. charts or diagrams), and then finally I start rewriting my bullet points into proper sentences, expanding my examples, and adding any interstitial text necessary to make things flow.
Also, I see some comments on keeping things short and to the point. In general, I agree with this, but depending on the medium, sometimes it doesn’t hurt to inject a bit of personality into your writing. Technical writing can be dry at times, and this can deter engagement. Try to use concrete examples whenever possible or refer to other supporting texts.
One of the big risks is that the cargo bikes are worth stealing with a truck or pickup. The resell value is great and even if the bike is inoperable, the parts can be easily dismantled and sold off. I worry that the tactics will shift more towards that direction as the bikes themselves get harder to ride off on.
Our threat vectors are a bit different in that the bikes are more likely to be snatched when the rider is dismounted and in a building for a pickup or delivery. We’ve been experimenting by keeping a GPS in the frame and triggering something akin to a car alarm when the bike starts moving too significantly while the rider’s phone isn’t in the vicinity of the bike.
Our primary challenge has been finding the ideal way to lock the bikes while dismounted. The best chain locks are too unwieldy to use for the pace our couriers move at. Wheel locks were interesting but would end up breaking spokes when couriers would inevitably ride them while still locked. We’re currently giving folding locks a go. Open to suggestions if anyone has ideas or experience with other solutions.
It’s been quite an interesting challenge. In particular, simple things like getting insurance or finding an auditor have been much harder, since the expertise in the nuances of how coops operate is fairly uncommon. The government itself often seems unsure on how to apply laws or administer programs in regards to us.
Financing was a challenge initially, though we’ve made some innovations in that area that have allowed us to access some VC funding.
On the other hand, such platforms can truly leverage the collective mass of its users, which is a distinct advantage it has over any traditional corporation. For example, we’ve been able to raise capital from our members who are also shareholders (and not simply just crowdfunders) and our client (member) acquisition cost has been significantly lower than our competitors, though it’s too early to say whether that’ll stay the course with scale.
I’m a bit surprised that this is making the rounds of HN though. OpenCV and other computer vision libraries have trivialized such counting applications for decades now. ML isn’t really necessary.
The watershed algorithm for example, comes built-in and allows segmentation which can then be followed up with blob counting: http://www.cmm.mines-paristech.fr/~beucher/wtshed.html
I don’t want to diminish OP’s work since the product seems to be well-developed and respond to a real need. I guess the challenge must have been making the app robust enough to support different workloads, lighting conditions, etc. I suppose the novelty factor is seeing to what extent the technology that we as developers and engineers work on every day is often disconnected from practical application.
Late 2019, some colleagues and I quit our jobs to move onto other endeavours with this as a side-project and since then it’s become a full time gig.
Often these programs require the fundee to get 30%-50% of the financing from non-government sources, so this could potentially count towards towards that figure.
Edit: Seems like organizations can’t apply, so maybe this point is moot.
In regards to the home page, we’re looking to retire it and put the restaurants in the forefront, turning the other one into some sort of landing page eventually.
I’m a developer and restaurant owner who created a restaurant delivery cooperative in Montreal, Canada. We’ve all been hearing the ills of the large delivery platforms for a while now and I wanted to throw my hat in the ring and see if it was possible to do something. Some colleagues and I quit our jobs towards the end of 2019 to start the project and we’ve been operational since around May.
We’re structured as a solidarity cooperative, meaning restaurants, employees (drivers, support, devs, etc.) and consumers are all members who can vote and take part in the profits of the venture (if any).
We have quite a ways to go before we’re a totally viable alternative to the other platforms but we’ve been having progress and positive feedback from our members. Looking forward to hearing your feedback and ideas.
The thing is, the the technical literature industry is kind of like venture capital. Publishers will throw a lot of things against the wall and whatever sticks will net them enough of a return to cover the rest. It can cost upwards of 50-100k to produce a book and most of them tend to flop. It’s really hard to understand which ones will flop as well, unless you have intimate domain expertise and can judge the technology and the community around it as well. At that point however, you may as well write the book yourself.
We all start somewhere.
The clicker makes things easier however.
Will be interesting to see where things go given they've switched suppliers for key parts supposedly in preparation for a 2019 release.
I can do whatever I want with it. I was surprised to find out after I joined that the regulations are really not that bad, less even than when I was at Microsoft. I think it really depends on the department and the function. The HR department for example is a lot more stringent (though believe it or not, they also explored VR with our team).
They have a pretty good set of tutorials on the HoloLens site, though they're kind of monotone and over polished for my taste. I think the key thing is to know Unity, which I've mainly done through doing and exploring their API or youtube videos. MVA is a pretty good resource, though I haven't needed to use it.
Things I like:
-Let's you have an infinite number of virtual monitors with applications such as word, outlook, browsers etc. -Developing for it is really easy with tools like Unity -Battery life is not too shabby, rarely have to take it off to charge while I'm doing something -Great demo piece
Things to work on:
-Field of view isn't terrible, but could still use improvement -Price point precludes a lot of consumer applications -Feels like you're always wearing sunglasses indoors. This takes away from the augmented reality bit as it can be pretty hard to interact with the real world sometimes (e.g. hard to read my real monitor when I have it on) -Gets kind of uncomfortable on your nose after a while, though that may depend on your face morphology -Interacting with voice commands in an office setting can be awkward/amusing -My colleagues think I'm never working