My spouse traveled to Canada for a few days. She just went a few miles over the border into Vancouver, BC.
She neglected to add an international data plan to her mobile number before she left. Because of this, she racked up $300 of data charges in 24 hours.
Every wireless carrier has at least one, and you have to add it to your account before you travel outside the country, and then delete it when you return home. But, why do I have to select it? My carrier knows when I’m out of the country! In fact, multiple systems between my cellphone and my account know it!
IP Street’s application runs on Python 2.7. Earlier this week, I evaluated all our Python packages for Python 3 support, as the first step in deciding when to migrate our codebase.
Although this was the time I’ve checked our packages for Python 3 support, I expected Django to be the only one that didn’t officially support it. (Production support is slated for version 1.6, which is now in release-candidate.) But Django is the only project whose development roadmap I closely follow! D’oh! Talk about a blind spot!!
This is why it’s good to sit down and formally check each package. Make a list of every package and check each one…
If you know someone who fits the bill, send them this post!
Title: Senior Developer
Reports to: VP Engineering
About IP Street
Founded in 2009, IP Street develops and markets software to help corporations, law firms, and financial analysts better analyze patent-related information. We make IP data easy to get, use, and understand!
We’re a start-up that’s developed a new way to visualize and data-mine intellectual property. We’re small and scrappy, have an innovative engineering team, and have built the business on awesome products that companies buy!
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 Celery, Postgres, Redis, and Solr. Our client-side code relies on Highcharts and Backbone, and supports desktop and mobile users.
This is “small b” big data, with lots of interesting challenges!
- Collaborate with others in product direction, priorities, and features
- Design, implement, and test new product (primarily but not exclusively server-side) features
- Some front-end coding and debugging, as needed
- Make the user experience as powerful, simple, and manifest as possible
- Be positive, flexible, and do what’s needed to move the company forward
- 10+ years experience in server-side development. Web development would be ideal, but it can be any kind of server-side code. We’re looking for expertise in processing pipelines or workflows, software farms, scaling, schema migration, etc. Or you’re a really smart person who loves complex software systems running on servers!
- Significant experience developing in Python or Python-based frameworks, on the order of at least 5 years or so. This must be serious development, not, “I write a 20-line script now and then.”
- Substantial experience in, and understanding of, a web framework such as Django. We’re looking for at least 3 years’ experience. Or if you don’t know Django, you’re eager to learn!
- Pluses: Significant coding experience interacting with (or experience in configuring) PostgreSQL, Solr, or another SQL or full-text search engine.
- Other pluses: Experience in or familiarity with jQuery, Backbone or equivalent technology, or client-side graphing packages. (These won’t be your focus, but the knowledge could come in handy.)
- Enthusiasm about modern approaches to software development, distributed version control, good coding and documentation practices, etc.
- You have excellent judgement in attacking complex tasks, and in balancing “good enough, now” vs. “much better, later”
- You’re self-sufficient when possible, and confident in setting standards
- You’re eager to build a small company into something insanely great!
- Excellent team and communication skills
- Bachelors Degree or equivalent in Computer Science or Software Engineering
Salary is DOE. Please send resume to john @ this-site’s-domain.
Jeff Bezos was in the news this week. Our local tech news site, GeekWire, published five posts about him. What are the most important traits of innovators? Have a willingness to fail. Bezos believes that truth shakes out when ideas and perspectives are banged against each other. Think long-term. Etc.
Some of the commentary was a tad critical of his personality. (Not in GeekWire, but elsewhere.) One observation (I don’t remember where I read it) was that he cared only about the business, to the point where he could make “hyperrational” decisions about what’s best for Amazon. Which makes him a great CEO, but maybe not such a great friend. If it’s true.
It got me thinking, not for the first time, that most entrepreneurial advice about starting a business is useless. Even if it comes from other entrepreneurs.
Jesse Noller, who works at Rackspace, volunteered to take a look at the underlying problems. He’s an awesome dude.
An update to an earlier post…
I’m replacing pyrax with something else in our system. The authentication errors and oddball failures still occur, and I’ve lost confidence that Rackspace will fix them in any reasonable amount of time. This is extremely frustrating.
Python-cloudfiles was way more stable, even though it wasn’t and still isn’t in active development. Maybe we’ll resume using that.
Thursday, I was irked by a bug.
I had modified a background task so it could import a range of documents from another subsystem into our datastore, instead of only one. Its parameters had included one “document id”, which identified the patent document to import. Now, it could be given that, or two document ids representing a document range.
In one instance, it reported a successful completion yet the desired patents weren’t loaded. What had gone wrong?
Multiple official and de facto formats exist for US patent application and grant document ids. To keep this simple, let’s consider US Design Patents. Their document id is a “D” followed by a number. This looks like “D4432″, or “D902″.
So if you wanted to import a range of Design Patents, you might say, “Import the patents D900 through D4000, inclusive.” “D900″ is the lower bound and “D4000″ is the upper bound. Right?
Not so fast!
>>> "D900" < "D4000"