mpfefferle

Columbus, OH | Remote or On-site | Full Time

Stack: - (Current) Ruby, Ansible, Puppet, JunOS, NETCONF, SLAX, Linux - (Previously) Java, C#, Symbian/C++

Resume: https://www.linkedin.com/in/mpfefferle Contact: matthew.pfefferle@gmail.com

I'm currently working for an established networking equipment vendor after having entered the company via a startup acquisition. My experience includes from mobile, enterprise, web, ops, people management, and lately, network automation. I'm coming up on 10 years work experience.

I'm looking for an organization that is trying to make a dent in the universe. I expect to have to wear multiple hats and learn lots of things on the fly.

POPFile has an IMAP module that makes something like this pretty easy to set up. You just need to connect POPFile your GMail account, set up some buckets for POPFile, and then tell it how to map those buckets to IMAP folders.

It takes a little time to train the filters, but once that's done, the accuracy is pretty good. My only problem now is coming up with a good labeling system.

This may not be a perfectly generalized solution, but is it possible to structure your system such that when upgrading from version i to version i+1, version i of your app is compatible with both versions i and i+1 of your database and vice versa?

Say, for example, your factoring a column into it's own table. Don't just drop the column, set up a trigger to synchronize the original column value with a value from one of the rows in your new table.

You could then finally drop the column in version i+2.

I seem to remember finding a book on database refactorings that covered this technique in more detail. It was online so you could try Googling for it.

When your company has no revenue, the "obvious" answer is to sell as hard as you can until your cashflow positive. But it's not going to help unless the product actually works.

This seems to be the gist of the comments here, but I'd like to propose a third requirement: operations.

Ultimately, a business has to become self-sustaining, and that can't happen until the acts of building the product and selling the product become sufficiently well defined that they can be handed over to a professional staff. (See also: E-Myth)

It'd be interesting to see how far we could take a loosely coupled network for Wordpress installs towards this goal. How actually to make that work is something I've been pondering lately.

Also, I think the work that Dave Winer's been doing around realtime RSS is a huge step in this direction.

.NET wasn't bad. It was Vista, Visual Studio, that busted Dell, and a mountain of legacy code that made my experience a nightmare.

Where do you find the historical data and the data feeds to start building such a system though?

Is there any meatier information on this topic?

StephenColbertium

I'm definitely having second thoughts. I'm probably not going to upgrade until my contract expires next summer, but when I do, I'll have options. A Palm Pre or one of the forthcoming Android phones plus Verizon will probably be enough to get me off the iPhone.

This is the only method that's worked for me: 1. Comb the job boards for interesting looking positions. Don't worry about being qualified yet. 2. Find the name and location of the hiring manager. 3. Write a personalized cover letter to that manager and tell them that you're interested. If you're not qualified for the position as advertised, tell them that you'd be interested in something similar. Sell yourself to them. 4. (This one's important) SNAIL MAIL your resume and cover letter in an 8.5 x 11 envelope.

The last one will make you stand out and tell them that you're really interested and not just spamming them.

Is this web van 2.0?

Who doesn't want a great big, GPS enabled, "FEED ME" button?

I thought the current rationale for not allowing cell phones and other wireless devices on planes was the potential for interfering with ground based communications. I didn't think they'd used the avionics argument in a while.

Does this mean that the enterprise is back in style again?

C++ with just a couple added limitations. Exceptions and static data are only now (in v9) starting to be supported. Assume that you'll use Symbian's app frameworks exclusively and not Boost, STL, etc.

I'd look at it but the domain makes me think its NSFW.

FWIW Symbian 9 allows static data in UI processes, uses a standard ARM ABI, and has a homebrew non-unixy security model called "Platform Security". I'm not saying it's a great platform, but they were starting to make progress before I abandoned them a year ago.

In theory J2ME has wide distribution, but in reality, the platform is highly fragmented.

I agree that the platform is pretty tightly locked down, and both of these issues make the platform useless for real development. If you want to write anything other than a Tetris clone, stick with an open platform.

This is the only Android book I'm aware of. I haven't read it though so I can vouch for it's quality.

http://pragprog.com/titles/eband/hello-android

The only supported language on Android is Java, so I'd stick with that.

This post has singlehandedly killed my productivity for the entire day.

This is more political than I'd like to see here, but I guess you could relate this concept to product design. If you have an idea of what's "best" for your users, you could arrange your UI so that that's how they use it.

Also, NewLC.com is a big community around Symbian development. They're a pretty good resource for tutorials and questions.

This is the book I learned Symbian/C++ on: http://www.amazon.com/Developing-60-Applications-Developers-...

It's a bit out of date and it focuses on Nokia's application framework (Series 60). It should be enough to get you writing basic applications though. If you're going to stick with Symbian, don't worry about C or STL. They don't use them.

I assume you're going to be using the more recent Symbian 9. Unfortunately, I don't have any books to recommend for this version. You'll need to rely on the Nokia/Symbian docs for Symbian 9 specific features like Platform Security.

Since you're new to C++, I'd recommend following Symbian's naming conventions religiously. They were very helpful when I was a C++ noob just starting out.

I haven't worked on Symbian in about a year, but if you have any questions, drop me a line (email's in the profile). I'll see what I can do.

A wiki would probably work well. A Google Site perhaps?

This is basically the rational behind the E-Myth. Your business is not just another job you do. It's a self-sustaining entity that you create.

Exceptional Innovation (www.life-ware.com). We design hardware and software for smart homes.

"Complete Idiot Officer"?

Gotta love Vista. Blue screens on boot up have become part of my morning ritual.