This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Was the fact that we were primarily using PHP essential, or could we add new tools written in other languages? Labels: productdevelopment 15comments: mukund said. Thoughts on scientific productdevelopment Lo, my 5 subscribers, who are you? What if someone wanted to write their module in OOP style?
This gets me into trouble, because it conjures up for some the idea that productdevelopment is simply a rote mechanical exercise of linear optimization. You just constantly test little micro-changes and follow a hill-climbing algorithm to build your product. They just ask "which hypothesis should I show?"
Most of this code was from a variety of open source PHP projects that were glued together with the shortest path to goal possible. When Eric writes, "By the time we started doing continuous integration, we had tens of thousands of lines of code, all not under test coverage." We had closer to several hundreds of thousands of lines of code.
As the product matured, they were able to ratchet up the quality to prevent regression on features that had been truly embraced by their customers. Second, leveraging a dynamic scripting language (like PHP) for building web applications made it easy to quickly set up a simple, non-disruptive deployment process.
be the manager and productdeveloper). Developer – Most likely your product requires some engineering. Make sure you have the right developer(s) on board in whatever capacity you need them, whether it’s a part time HTML or Wordpress developer or a full time PHP wiz.
Why vanity metrics are dangerous ► November (1) ► October (7) ► September (9) ► August (8) ► July (8) ► June (7) ► May (8) ► April (5) ► March (11) ► February (10) ▼ January (10) Achieving a failure Refactoring yourself out of business Three freemium strategies Lean hiring tips Why PHP (..)
In addition to my first official commit, WePay also just hired Rasmus Lerdorf , the creator of the PHP programming language. At some point, I’ll write another post about what a non-engineer does, or should do, during the early stages of productdevelopment. So, without further ado, what I’ve learned: Don’t be Helpless.
In addition to my first official commit, WePay also just hired Rasmus Lerdorf , the creator of the PHP programming language. At some point, I’ll write another post about what a non-engineer does, or should do, during the early stages of productdevelopment. So, without further ado, what I’ve learned: Don’t be Helpless.
Meanwhile, we were building our app in PHP, using a generic DB driver and mysql, "for the time being." Thoughts on scientific productdevelopment Lo, my 5 subscribers, who are you? We tried to learn how to create a schema, or really anything at all, and mostly failed.
Why vanity metrics are dangerous ► November (1) ► October (7) ► September (9) ► August (8) ► July (8) ► June (7) ► May (8) ► April (5) ► March (11) ► February (10) ▼ January (10) Achieving a failure Refactoring yourself out of business Three freemium strategies Lean hiring tips Why PHP (..)
I know some of those compilers are no longer available (some are hosted, others are not), so I took the liberty of putting up a copy of the PHP Greasemonkey Compiler. Thoughts on scientific productdevelopment Lo, my 5 subscribers, who are you? As I make more, youll find them (with source) at my Greasemonkey Compiler page.
Why vanity metrics are dangerous ► November (1) ► October (7) ► September (9) ► August (8) ► July (8) ► June (7) ► May (8) ► April (5) ► March (11) ► February (10) ▼ January (10) Achieving a failure Refactoring yourself out of business Three freemium strategies Lean hiring tips Why PHP (..)
In fact, ideally, we want our users never to touch any code (be it HTML, JavaScript, CSS, or PHP). So, VWO is suited for people who don’t want to rely on developers or IT team for doing even the simplest kind of testing (thereby lengthening the time involved in getting the test up and running).”. That’s not a small accomplishment.
We need whomever is responsible for productdevelopment and/or ops to, effectively, carry a pager for drop-everything-and-do-it-now resolution of security issues, just like we’d do for e.g. the server has fallen over or “our building is, physically, on fire.” (And gulp their dependencies.).
In fact, ideally, we want our users never to touch any code (be it HTML, JavaScript, CSS or PHP). So, VWO is suited for people who don’t want to rely on developers or IT team for doing even the simplest kind of testing (thereby lengthening the time involved in getting the test up and running).”. That’s not a small accomplishment.
In fact, ideally, we want our users never to touch any code (be it HTML, JavaScript, CSS, or PHP). So, VWO is suited for people who don’t want to rely on developers or IT team for doing even the simplest kind of testing (thereby lengthening the time involved in getting the test up and running).”. That’s not a small accomplishment.
Why vanity metrics are dangerous ► November (1) ► October (7) ► September (9) ► August (8) ► July (8) ► June (7) ► May (8) ► April (5) ► March (11) ► February (10) ▼ January (10) Achieving a failure Refactoring yourself out of business Three freemium strategies Lean hiring tips Why PHP (..)
Or, for something more substantive, how about the top five-most-read posts: Why PHP won Dont launch Five Whys Work in small batches The engineering managers lament But wait, theres more! Read the very first comment (thanks tfitz!) or relive my very first subscriber survey - when there were a grand total of five. First OODA reference: Ideas.
Why vanity metrics are dangerous ► November (1) ► October (7) ► September (9) ► August (8) ► July (8) ► June (7) ► May (8) ► April (5) ► March (11) ► February (10) ▼ January (10) Achieving a failure Refactoring yourself out of business Three freemium strategies Lean hiring tips Why PHP (..)
Why vanity metrics are dangerous ► November (1) ► October (7) ► September (9) ► August (8) ► July (8) ► June (7) ► May (8) ► April (5) ► March (11) ► February (10) ▼ January (10) Achieving a failure Refactoring yourself out of business Three freemium strategies Lean hiring tips Why PHP (..)
Why vanity metrics are dangerous ► November (1) ► October (7) ► September (9) ► August (8) ► July (8) ► June (7) ► May (8) ► April (5) ► March (11) ► February (10) ▼ January (10) Achieving a failure Refactoring yourself out of business Three freemium strategies Lean hiring tips Why PHP (..)
The technical interview is at the heart of these challenges when building a productdevelopment team, and so I thought it deserved an entire post on its own. Still, a startup productdevelopment team is a service organization. Labels: hiring , productdevelopment 5comments: TedHoward said.
Everyone has to be a generalist and able to work on any kind of problem - specialists will be (at best) somewhat bored and (at worst) highly distracting because they want to steer productdevelopment into whatever realm they specialize in. Stage 2: The first hires. Early on, specialists are rarely desirable.
Lessons Learned by Eric Ries Monday, January 12, 2009 Why PHP won When I first learned to program on the web, Perl + CGI was the dominant platform. But by the time I was building my first websites for commercial use , PHP had taken over. Writing unit tests or mock objects in PHP is an exercise in constant frustration.
When Linus started what later on became Linux, he was at best a wet behind the ears developer. When Zuckerberg started Thefacebook.com he was a PHP coder (translation: not a real developer). I mean a rockstar developer, you need a reliable, steady, bull-like technical partner. I'll give you a 50% here.
sites from scratch - Experienced with the majority of the social api’s (Facebook, Twitter, YouTube, Meebo, PayPal, Flickr) - Experience managing offshore dev teams - Most recently a Director of ProductDevelopment at an early stage funded startup [link] meeblog » Blog Archive » starting up: finding your co-founders [.]
Without conscious process design, productdevelopment teams turn lines of code written into momentum in a certain direction. This is why agility is such a prized quality in productdevelopment. As far as I know, there are no products that are immune from the technology life cycle adoption curve.
Because, unless you are working in an extremely static environment, your productdevelopment team is learning and getting better all the time. Most importantly, I encouraged the leaders of the company to bring awareness of the business challenges to the productdevelopment team. Great post, Eric.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content