We're at about one legislature for every 30k people. It was one per 20k in 1973, one per 12k in 1919, one per 6k in 1889, and less than one in 2k when Minnesota was a territory in 1858.
I'm not sure what the right ratio is, but the level of disenfranchisement is palpable.
I originally agreed with you, but I've struggled communicating how RCV works to rural Minnesota. I've found more personal success communicating this model.
"We" is going a long way here. I have yet to meet someone in rural Minnesota that is aware of this problem, and that there are alternative solutions like this one.
But to your main point: the will is not in publishing this, but in spending every day winning hearts and minds in small town bars and community centers. I could certainly use some help.
I think the number of representatives per election district is a really interesting mathematical/social problem in democracy, and I’m interested in what this audience has to say.
If you live in Minnesota, please consider helping me transform rural politics. I’m the chair of the Agrarian Party of Minnesota [1], and candidate for the 20B legislative seat. Please consider running for office and providing a new hope for republicanism. I also seek help moving our statutes to a version control system, among other technical tools.
Those initial leaves are its cotyledons [0], and they are part of the seed embryo. These leaves often die off shortly after the emergence of the plant's first true leaves, but apparently can last for a year or more in some species.
Love the Rebuilding Rails concept! I'm doing a very similar thing in Ruby, focused more on "web application development from first principles" (https://theodorekimble.ck.page/e0bb43b156). I know I better absorb concepts if I can trace them back to a more fundamental "truth".
Curious to hear if anyone else has found success with Rebuilding Rails, and what they found most helpful.
If you want to do the same thing (build up from 1st principles) with CSS, I ravingly endorse Axiomatic CSS as defined and implemented in https://every-layout.dev
Disclaimers: no affiliation, just a very satisfied customer. IME the free content alone is illuminating, and having paid $100 to access to the full "book" incl all the layouts' implementation it was a bargain.
I found Outreach last year on a "Who is hiring?" thread myself and joined the team shortly thereafter. I'm now the lead for one of our two platform teams and I'm looking to hire experienced software engineers to help us scale our backend systems.
Outreach is a sales engagement platform. We've got great customers (https://www.outreach.io/customers/) and have raised around $60M to date (through a series C round). We just moved into a new office in the Fremont/Wallingford neighborhood of Seattle. We pay competitive market salaries and offer excellent benefits. For example, I just returned to work from four weeks of paternity leave and was welcomed with eight weeks of paid postpartum doula support; I can't express how thankful my family was to have four well-rested nights of sleep each week.
Our team is working to scale our monolithic Ruby on Rails application as our customer list continues to grow. We own our core CRM, API platforms, background frameworks and our bidirectional syncing systems with Salesforce. In addition to Ruby/Rails, we use MySQL, RabbitMQ, Elasticsearch and Redis.
For the backend role, I am particularly interested in individuals with strong software design/architecture skill sets and those who excel at managing complexity.
Please reach out to ted.kimble@outreach.io if you are interested. We also have a number of other engineer opportunities available, including roles in front-end development (React), data science and machine learning. See our careers page for all job details: https://outreach.io/company/careers/.
My Jekyll work flow tends to involve: Write a blog. Publish. Recognise horrid markdown bugs. Go and fix already published blog.
I appreciate there are better workflows, but as a Windows user I'm not going to install Jekyll to publish locally and test, nor is my blog big enough to justify a test environment.
The "drafts" feature basically just takes a draft and publishes it. What would really make life easier is it the drafts feature would "publish this blog, but don't update the front page to link it". I could look at it knowing the URL, and get it right first.
That's my main use case. I've got my personal blog [1] setup as a Static Website Manager repository and connected to my personal AWS S3 bucket.
Whenever I need to make a little change I can edit locally in my editor of choice, commit and push to SWM where I can preview the changes before merging to my production bucket (all without installing Jekyll locally).
If I don't have my machine, I can also just login, edit the text and then follow the same preview/merge to deploy workflow.
As a fellow Windows user (at least at home) with a Jekyll blog deployed on GitHub pages, I would recommend using a web IDE such as c9.io or koding.com.
They are little VPSs with sudo access (and a private web server) so you can test "locally" there and then git push once you're ironed out bugs. In your Windows machine you only need a web browser.
Something that's possible with some static engines but not really catered to is the ability to include the contents of other markdown files into a page-
----page----
# Title
<< contents of /markdown/file >>
<< second file >>
<< third file >>
Useful if you have lots of sections that you want to combine in different ways, and update them all at the same time...
I recently launched Static Website Manager (https://www.staticwebsitemanager.com) which aims bring static sites to a non-technical market. Would love to chat more if you have questions.
Looks cool, but at first glance (screenshots) it appears to lean heavily on a "git"-like model with branching and merging and rebasing. These are not concepts that I would expect a so-called "non-technical" market to understand or embrace. Something much simpler may be required for such people.
Looks pretty cool. Normally I would want something I could self host on Heroku but this looks like something I could consider recommending to clients who wants a simple CMS.
I'm not sure what the right ratio is, but the level of disenfranchisement is palpable.
reply