It's hard for me to read this any other way.
What was the thought process there?
if you do go down this route, I would suggest avoiding a model with an LED in it. while it looks cool for sure the LED is positioned so that shines right in your eyes if you put the device front and center (like in between a split keyboard).
I enjoyed working through Clojure for the brave and true: https://www.braveclojure.com/clojure-for-the-brave-and-true/
and the go tour is probably the best introduction I've ever had to a language: https://tour.golang.org/welcome/1
A few months back I saw a comment[1] from one of the stripe co-founders where they mentioned they were thinking about "pace layering" and how it applied to their company and processes.A quick google turned up an interesting article summing up a concept with the same name[2] by Stewart Brand. In the Acknowledgements section he mentioned a chapter in his book, which I tracked down and read[3]....
- Incident report
- Scheduled down time
1: https://vimhelp.org/pattern.txt.html#gd
Day-to-day maintenance (replacing lightbulbs, shelf falling down etc) is your responsibility. Plus you get to decorate however you want (at your cost). All other taxes and maintenance costs are shared proportionally.
> Who gets to decide when to call the plumber?
You do. There's a home emergency cover plan in place (costs shared proportionally) so you can get someone round 24/7, 365 days / year.
> If you fail to pay your rent, can they evict you?
Yes, but if you just need a couple of months to get back on your feet, we won't.
> What happens to your share then?
You still own it, but any rent arrears would be netted off.
> Can you sublet?
Not at the moment.
> Can you sell your share on the open market, or only back to the company, at whatever price they decide is fair market value?
The latter, but there is an option to go to the open market together. Price is determined by a regulated independent surveyor, not by Unmortgage.
https://www.unmortgage.com/faqs
https://www.unmortgage.com/how-it-works
source: I am an unmortgage employee.
https://github.com/farrellm/scad-clj
This is biggest project I know of that uses it:
Millions of people are stuck in the rent trap, with no way to own a home. At Unmortgage we are reinventing homeownership to bridge the widening gap between renting and buying with a mortgage.
We are funded for the next 3 years after the largest seed raise in Europe and are looking for people to join us at this early stage.
We work in a Agile (XP+TDD) team in a stunning office above Bank station, London. The Stack is React, Python running on Kubernetes in Google Cloud. Everyone gets their hands dirty and there are no silos allowed.
Here are all our exciting jobs: https://jobs.lever.co/unmortgage/
If you have any questions about the backend jobs you can drop me a line at [email protected], or [email protected] for the frontend jobs, or alternatively our CEO [email protected] for all of the above and any additional information about the company.
I feel like a lot of these features could be handled with git-notes[1]. For example git-appraise[2] uses the git-notes feature for a code review system:
http://www.keyboard-layout-editor.com/
to design your layout, then
to design a layer case, files go to a laser cutting service,
then you would need a controller of some sort (commonly something like a https://www.pjrc.com/teensy/), switches, diodes, usb ports, etc.
then hand wire everything together.
tmk/qmk is more or less a defacto standard in custom keyboard firmware:
https://github.com/qmk/qmk_firmware
here are some examples of people generating firmware with webtools, I don't know what they use on the backend.
We are a smallish tech team (11 developers) actively developing a product where downtime has immediate negative revenue implications.It's starting to get difficult to ship changes without breaking something somewhere.so my questions are:1. what is your teams approach to quality assurance2. what is your teams approach to quality control3. at what point does it make sense to hire dedicated staff...
>>> ranges = [range(i) for i in range(5)]
>>> [*item for item in ranges]
[0, 0, 1, 0, 1, 2, 0, 1, 2, 3]
>>> ranges = [range(i) for i in range(5)]
>>> [item for subrange in ranges for item in subrange]
[0, 0, 1, 0, 1, 2, 0, 1, 2, 3]