Carrot is a SaaS that provides online marketing tools for real estate investors and agents. Members use our website builder and other content marketing tools to create sites optimized for the leads they wish to capture. Those leads flow into our suite of marketing tools for action and analysis. We are one of the most popular options for real estate professionals wanting to generate leads online, and are used by thousands of individuals and companies.
Carrot is Oregon based, but you’ll be joining our fully remote development team. We’re looking for a full stack developer to join our team and create new features, maintain and improve our React web app, build on our Ruby on Rails REST API. Our platform hosts almost 12,000 active websites right now so you should be ready to build systems that scale. You'll enjoy working with us: we have a fully-staffed product team, fully-staffed SRE process, fully-automated CI/CD pipeline, great code-review process, and we use GitHub and Slack to collaborate. Join a small, high performance SaaS team that dominates its vertical!
Hey Ben! This is so neat! I worked with Dr. Hansen on the audio digitization over on http://exploreapollo.org. Thanks for the link in the footer! I’ve been out of the loop on that project since graduating. Regardless, if you want to collaborate shoot me an email austin@austinpray.com
There are two different AR-15s: ArmaLite AR-15 which is what the article is about and from which M16 was derived and then modern day Colt AR-15 which is civilian version of M16.
There are a hundred (at least) vendors who make AR-15 pattern rifles, Colt's patent expired several years ago.
The Armalite AR-15, the Colt AR-15, the Colt M4, Colt M4A1, FN M4A1, and the military M16, M16A1, M16A2, are all the same weapon with minor modifications. The significant differences are barrel length (interchangeable among most if not all), upper (slick side or with forward assist, not consistent among any of them), buffer weight (generally the full-auto versions have a heavier buffer), trigger model (full auto, 3rd burst, and semi-only -- many variants exist and are interchangeable among most models w/ exception that the civilian models do not have the upper hole that allows for the full-auto trigger components to be installed).
I brought this up with my Japanese friend. He told me there are so many homophones in the language people are desensitised to stuff like this. For example: シ (shi) can mean both 四 (four) and 死 (death).
You’re not wrong, but your choice of examples isn’t great. Four is actually associated with death because it sounds like death, four is unlucky[4]. There is also an alternative pronunciation for “four”, よん。
The fact that it couples dependency management to virtualenv management is really unfortunate for people that use docker. Can’t wait for pipfiles and such to be native to pip.
It seems definitely promising; it depends on how much adoption it's going to take. Even the most interesting languages (like Nim, for instance) struggle these days without corporate backing.
Worth pointing out maybe that MyPy is not a language but a type checker that works with regular Python. I've been getting into the habit of using it on everything I do lately and find it extremely useful. You can even do runtime checking on the types with tools like Enforce [1], and the Molten framework that was posted on here last week [2] uses MyPy typing as a core part of the framework.
It’s toxic and lazy too. You should first go look and see if the actual code is high quality/does what you want.
If your idea of shopping for dependencies is looking at the amount of GitHub stars and the quality of the documentation: you are going to miss some real diamonds in the rough.
Is it laziness or efficiency? It's, in my read, a heuristic (he even uses that word) for deciding whether it's worth spending time reading the docs before looking at the actual code, to see if it does what he wants.
It's about how he should best spend his time, which is finite, after all. Paid time even more so.
I evaluate projects by (1) actually reading their source code, (2) looking up their frequency of updates and release packaging, (3) the community interaction of authors and contributors.
The total amount of effort it took to write that blog post could have been spent on submitting PRs to improve documentation of various projects.
