8,092 karma · joined July 14, 2010
Email: kevin@burke.dev
Current & past projects: kevin@burke.dev
Code: github.com/kevinburke, bitbucket.org/kevinburke
I write here: kevin.burke.dev
Twitter: @derivativeburke
[ my public key: https://keybase.io/kb; my proof: https://keybase.io/kb/sigs/JFgvOkXSINpPmFfGxbbEg070B9zHplGJdtAV1-bv7D0 ]
Per California HCD, Davis issued permits for about 1350 homes between 2013 and 2020, or roughly, Davis grew by about 4.5% in that time frame.
California grew its population by about 6% between 2010 and 2020 and the total housing stock by about 5.2% which puts Davis at just about average in terms of construction, far from "tons." https://www.census.gov/library/stories/state-by-state/califo...
Also the same rules currently apply in Redondo Beach which is a little bit more expensive.
(The submissions are staggered across the state; the Bay Area’s deadline is later than Yolo County’s.)
There's no requirement that the developer is a public agency and only 20% of the apartments must be made available to families making $74,000 or less.
This is far into the salary scale for Davis School District educators, for example. https://resources.finalsite.net/images/v1593632639/davisk12u...
I'll also note that the alternative to infill housing is single family home suburban sprawl, which is a lot more taxing infrastructure wise - apartment dwellers use less water, less electricity, and are less likely to own a car than suburban single family homeowners. Further the consequence of less homebuilding in California is more homebuilding in places like Texas, which are a lot less friendly for the environment.
Like Los Altos Hills could mandate that new apartments be covered in real gold, but they don’t do that.
It's just that you probably want the biggest building possible so the potential profit is worth the years of delay while inevitable legal challenges and possibly an EIR work their way through the courts and planning process.
I guess in your eyes I should have also done the cryptography, however, I am not a cryptographer or a mathematician and one of the first things that you learn when you start doing work with cryptography is that you shouldn't roll your own crypto.
I decided to make that library prominent because in my consulting practice I saw a lot of clients using cryptographic primitives that were clunky and/or had a lot more overhead, for things like cookies or public key authentication or just sharing messages. nacl is difficult to use incorrectly, and is fast and efficient in terms of overhead. I wanted to promote use of nacl more than the work that I was doing for it in particular.
For that client (a smart lock company), I rewrote the backend, that someone else wrote in C for a specification that did not match the needs of the business. The C software was extremely difficult to read and maintain - socket writes in a callback in one part of the code and socket reads in a completely different part of the code, shelling out to curl, simple Mongo queries that would take 50 lines to set up. As a result the engineering team could hardly make any progress deploying new features. I ended up rewriting the whole backend in Go, a few thousand lines of understanding what the C code was doing, and porting it, to the point where the team could actually release patches and new features on a regular cadence, and figure out what on earth was going on with the Mongo queries and shell-to-curl.
That's not public though, if you're looking for public work, you could look at Logrole (github.com/kevinburke/logrole), a HTML client for your Twilio call, SMS, phone number, and recording data. Of course, you could say "that's just a regurgitation of whoever did the API client", which is true-ish, but I also wrote the API client (github.com/kevinburke/twilio-go). Of course, you could say "that's just a regurgitation of the Twilio API," but I also helped build and maintain the Twilio API, as well as the documentation and information architecture (https://www.youtube.com/watch?v=sQP_hUNCrcE), and the client libraries (https://www.youtube.com/watch?v=C_UJHqR_2Mo).
Most recently I was hired as the first engineer at Meter (meter.com) where I built out the entire backend API, the deployment infrastructure, the CI/CD infrastructure, a pipeline for the in-the-field servers to update themselves, and a method for access points to retrieve configuration from the backend. All in all this was probably about 30-50,000 lines of code over two years. I think the API has had one customer facing error in two years and no downtime.
It is true that anyone can call themselves "a software engineer" but not everyone can get contracts for a sole member consultancy and, crucially, get their contract renewed multiple times at every single client. If I was selling snake oil and not delivering anything, that would not have happened.
So whether you would be good at the job being hired for, then.
The whole point of the post is that the phone screen isn't just screening for deal killers. If it was you wouldn't flunk people for not nailing the optimal Big O runtime for your custom algorithm.
I’m very capable of focusing when there is a lot of money on the line.
(I’ve also submitted code that solves the problem “perfectly” and been rejected, no idea)
The Surgeon General happens to be a pretty easy example, but there are many, many others, at every level of US government.
Data about allergic reaction rates, infection rates, and conditions that are ideal for spreading COVID are all public and not in dispute. My argument is a straightforward application of that data to the facts.
I don't think arguing from authority has a really great track record this pandemic.
The argument on the blog is pretty straight forward, and the data is all public.
I will say though one trick I've seen (I should write about this) is multiplying your common stock through by the latest price of the preferred stock and presenting this as the "current value" of your equity offer. Your common stock is not worth as much as the preferred stock.
I alluded to this in the post - this wasn’t the only thing I did wrong, not at all, but it was by far the easiest to change and the clearest signal to the interviewers that I was overconfident and incurious, and the other stuff would just detract from the message that’s already there.