If your cookbook contains a cheesecake recipe, and it says to bake the cake for 10 minutes so a light skin forms on top so the Heath Bar Toffee chunks you now add will stay on top while the cake continues to bake and form a delicious and visually appealing topping, and in fact no skin has formed and the Heath Bar Toffee chunks sink into the cake like naval depth charges, because the “10” should have been a “40,” then your book was sloppily edited and you deserve to have raw ginger pounded up your nose.
I’ve used Aquamacs for the past four years or so. It has its strong points.
But I’ve always been a little unhappy with its slow performance relative to native Emacs (I use a MacBook Pro), and its unique initialization and behaviors. I’m sure there are good reasons for every difference. But each difference, no matter how small, is a little more cognitive load. E.g., I never got used to M-x Info opening up in a new window somewhere on my screen…
Today, I decided to try Emacs for Mac OS X. Whoa! I love it! It’s Emacs, the whole Emacs, and nothing but the Emacs. Win!
I even donated $50 to the project. So there!
After my embarrassing post about anaconda, I’ve awakened a Jonesing for working again in Lisp. I think I’ll look for a project to contribute to — maybe start by fixing some minor bugs in an Emacs package, or something similar.
When setting up your .emacs to automatically add company-anaconda to your company-backends list, eval-after-load is your friend:
;;; Company, and Company backends. (add-hook 'after-init-hook 'global-company-mode) (eval-after-load 'company (progn '(add-to-list 'company-backends 'company-anaconda) ))
I just got my annual flu vaccination at Bartell Drugs. $29.99. It was quick and easy.
My employer-provided insurance company, United Healthcare, won’t cover it. Why? Because it wasn’t done in a doctor’s office.
Same vaccination, no difference in effectiveness, but it’s covered only if administered by a doctor.
This is insanity.
If you use Emacs and Twitter, give TwitteringMode a try. It won’t replace your favorite client, but you can easily follow a list without leaving Emacs and do most things (reply, RT, etc.) with it. No image posting, but it can optionally display avatars.
Just registered for PyCon 2015. Yee haw!
Founded in 2010, IP Street has built the world’s preeminent Intellectual Property(IP) analytics and visualization engine, in conjunction with a nationally recognized IP law firm. Our SaaS product helps corporations and financial analysts quickly and efficiently analyze IP information. We make IP data easy to get, use, and understand!
As with any organization, we’ve continued to evaluate new ways to provide value to our clients. We’re evolving into a “SaaS+” model, which pairs our service with expert consultation to assist our clients in assessment and evaluation. Our focus remains on the financial and technology markets.
Our technology stack is almost all open-source, with some nifty esoteric search technologies. Most of your work will be in Python and Django, in a Mac-based development environment, deploying to Linux. Other technologies include Postgres, Redis, and Solr. Our client-side code relies on Highcharts and Backbone.
This is a “small b” big data firm. But since we’re a scrappy start-up, we don’t have a big firm’s resources. We compensate by hiring senior people who are self-directed, appreciate real-world development trade-offs, and have a can-do attitude. It’s OK to not know something if you’re eager and willing to learn it. We know that bad code always haunts, so if you enjoy writing good code using a language’s standards and idioms, you’ve come to the right place!
This position is in a small engineering team. Its focus is on server-side work, which includes poking fingers into PostgreSQL, Solr, and other technologies. So, it’s not just coding. We do feature design, development, testing, DevOps, some customer support, and work closely with product management. Did I say that we wear multiple hats every day?
On to the details…
- Collaborate with others in product direction, priorities, and feature design
- Design, implement, and test new product features and bugfixes
- Make the user experience of our products as powerful, simple, and manifest as possible
- Do what’s needed to move the company forward!
- Significant server-side development experience. We’re not hung up on a number, because one year for you could equal five years for someone else. We’re looking for the confidence and awareness that comes from working with server-side web code. Here are some keywords: Subtasks, sentinels and software locks, software farms, scaling, and schema migration. If you’re a smart person who enjoys working on software systems running on servers, you can check this box.
- Significant experience developing in Python or a Python-based framework. We’re a Python and Django shop, and there’s no PHP, Ruby, or Perl within 2000’ of our codebase. This must be serious development, and not, “I occasionally write 20-line scripts.”
- If you’re very experienced in another language and are eager to learn Python, that could be OK. Can you convince us that you’re looking for a great opportunity to learn?
- If you don’t know Django, that’s fine — it’s easy to learn.
- Abilities that are nice to have: Significant interaction with PostgreSQL, Solr, or another type of db/search engine.
- You’re enthusiastic about modern software development, distributed version control, coding, documentation, testing, and teamwork.
- You have excellent judgement in attacking complex tasks, and in balancing “good enough, now” vs. “much better, later”
- You’re self-sufficient, and confident in setting standards
- Good communication skills
Salary depends upon experience. Please send your resume to email@example.com.