leftnode

I ask this question as well. I work mostly with PHP developers and it's telling most of them don't have an answer or only say "consistent function argument order".

If you claim to have 7+ years using a language, surely there's a list of things you could add to make it better.

I think it's standard in the PHP ecosystem though.

His show "Louie" is equal parts drama and comedy. It's really an amazing show and he's easily the top comedian today, hands down.

Facebook also has some unique traffic problems that almost no other startup is going to experience.

I use Phing to download whatever version I want during build time and to place it in a lib/vendors/ directory. So, for example I use pieces of Zend and the Google AdWords PHP SDK with my recent project, so in a build.settings file, I have:

google_adwords_version=2.6.4 zend_framework_version=1.11.6

Then, Phing will read in that file and convert those to properties. From there, I can wget the versions of those packages, untar them, and place them in lib/vendors/.

This makes it very simple to test with a newer version. Just update the file and rebuild and a newer version will be downloaded and installed.

I'm not sure of the technical details, but the data on LiveDrive may only be decrypted with a key that Backify has, and thus LiveDrive couldn't give you your data in a useable format.

From what others have said, I'm inclined to agree with LiveDrive. We'll see what ultimately happens though.

She may have only just checked in recently.

This is neat. Coincidentally, I helped build a site a while ago with much less design polish, but essentially the same idea.

http://nooges.com

Essentially a daily topic was posted, and people could disagree or agree.

Hope your site does well.

Thanks for the link, I'll check it out.

fetch_column() does essentially that. You can pass in the column number you want fetched, in this case, it would be the 0th column.

Yeah, that's exactly what I meant by it.

That looks interesting. I'll give it a look.

I'm interested in your counter arguments too. I'm sure there is some component or aspect I'm missing.

There's always the possibility you increase your price and no one leaves. Companies do this all the time.

From time to time I go by software mechanic since I spend more time fixing existing software than writing new software.

The recent High Scalability article outlining the Stackoverflow and Stackexchange network is worth a read.

http://highscalability.com/blog/2011/10/24/stackexchange-arc...

Joel makes some good points on why they stayed with physical hardware.

I personally wrote thank you cards to our first hundred or so customers. It really goes a long way to show some sort of personalization.

At my last job, every developer was a Senior Engineer. I chose Software Mechanic as my title.

As a former Quickoffice employee, I love seeing people actually using the app.

If it was the migration I was told about, no, they give you about 2 weeks notice that they're going to do it on X date.

I wish you the best, but getting a school to pony up for this is going to be difficult. Their budgets are extremely tight (at least in Texas). My wife is a teacher and she frequently finds her spending her personal money on classroom supplies.

Mine has expressed an interest of becoming a lawyer at the prestigious Dewey, Cheatam, and Howe law firm.

A new datacenter.

Slimtimer - http://slimtimer.com - it's pay what you want model.

As someone who doesn't own either but is looking into a more expensive chair, can you clarify either of those sentences?

Dallas, TX - SpeedFC (http://www.speedfc.com)

The company I work for, SpeedFC, is looking for some excellent PHP developers to build our ever growing team. We're currently a team of 11 developers with 4 team leads and 7 developers (I'm a team lead but do plenty of development too).

We do end to end e-commerce. We handle the websites of our clients (you may touch on this, but not often), the backend warehouse software (what you'll be working on), customer service, and fulfillment. We own 100% of our code, it's all written in house so you'll definitely have a chance to work on new products with fresh code. Now, you will also have to work on old projects with old code. Comes with the territory.

Our stack is full Linux, Apache, Postgres, and PHP. Even if you're not familiar with Postgres, but have a good PHP and SQL database background, still apply.

Why you would want to work here

We work with a tremendous amount of data and ensuring it's correct at all times is a difficult job. So, if you're in for a challenge, working here is great. Now, there are some downsides. We have an old codebase, largely untested and undocumented. You'll have to work on some stuff that will want to make you tear your hair out.

That is now changing! All code developed on my team is unit tested, documented through tests, and fresh PHP5.3+. We do code reviews, demo days, and have an official QA department. Also, right now my team is about to start working on a difficult and far reaching data synchronization problem. Thus, if you want to be a member on a project building code from scratch and "doing it the right way", now would be a great time to join my team.

Another nice aspect of the job: if you think something needs to be done, write up a short document explaining why and the benefits it will have, submit it to the bosses and get it approved. The executives are more than willing to let you work on fresh projects that will help the company.

Mix the good with the bad, and overall it's a good place to work. They just built us our own custom private office for developers only so other employees can't come bug you easily.

We won't help you relocate, unfortunately.

Availability - Now

Benefits

Health, Dental, and Vision. You don't start off with an incredible amount of PTO, and Christmas time is pretty nuts around here, but they say they're working on it, so we'll see what happens.

I will be your team lead. I won't be your boss. I won't know your salary, for example. I like working closely with my team members and bouncing ideas off them. I'm more than open to using different technologies where they fit and moving away from PHP where necessary.

Email me vcherubini@speedfc.com with your resume attached. I'll be doing the interviews, and I keep them very much functional and not theoretical. You won't have to bust out your college text books to remember what a red/black tree is, I want to know your past and current projects, and have a good discussion about you as a software developer, not an algorithm memorizer.

Not necessarily, for some client work I've reduced my price in exchange for full ownership (or rather, co-ownership) of the product I've developed. That way I can do with it what I want.

It's a bit easier when you already have a user base of billions.

Edit: So I disagree with the article entirely, it's not interesting at all.

Totally off topic, but that is an amazing Javascript library. Thank you.

I agree 100%. I tried to use and write a nice ORM but they usually get overly complex quickly, or are too simple. Now, I don't mind writing a simple boilerplate parameterized SQL query if it means my database access is lightening quick and I have the option to write as simple or as complex queries as I need.