Hacker News new | ask | show | jobs
by wynand 5409 days ago
I have respect for people that can deliver, regardless of what they use. The allure of cool tech is strong but tech doesn't make products: people do.

I cannot see what is wrong with your using plain PHP if you can get the job done faster (as long as you avoid things that make exploits easy, such as raw mysql db functions). When the time for a framework comes, you'll know.

Stop worrying about what others think and good luck!

3 comments

Delivering version 1 is very different from delivering version 2, 3 4... That's when the real test of engineering is.
Not just because this is what I do, mainly, but it's such an important point that it deserves highlighting. Working software is easy. Working maintainable software is harder.
I think the article is flawed in many ways, but if you define 'working' software as software that works for users in such a way that people actually want to use it, then working software isn't so easy. And getting from nothing to working software is harder than getting from working software to maintainable software. Or at least it's better understood.
Ha, I'd say non maintainable software isn't working. Just matter of time until it's broke or needs updating.
here's how I learned Python without noticing it:

(I had a background in PHP, JS, C++) 1. Off hours on 2-3 days with dive into python 3. 2. A month later - 'oh let's do this in python!' on google code jam 3. 'python challenge? that's cool' - one night hackathon a month later 4. 'I hate php, I'll do this new web app in django' 5. Two days messing with django 6. Five days and the app was done.

I don't know if I write 'best practice' python or django but it's about x6 less code than in PHP. I can rewrite my app completely in 2 days.

For me, the biggest problem in learning a new technology is finding the balance between cowboy hacking & analysis paralysis.

>I don't know if I write 'best practice' python or django but it's about x6 less code than in PHP.

Just curious... Surely you mean django vs php (not zend or some other framework - which _would_ have been the fair comparison.

I think he compared before (plain php) and after (invested time in learning some new technology).
No, the weird thing is I'm comparing Django to Kohana. The app I worked on in PHP was more complex, but one API page was very similar in both apps:

- Kohana: ~200 lines of code. - Django: 15. Seriously.

It's not only a matter of LOCs, it's also that writing code should be enjoyable. Python is, PHP not so.
Story of my summer Except now I have couple hundred of lines of "legacy" PHP that's not being written in Python just yet and considering time constraints won't be. It makes crossover projects hard.
+1 to both of you!
Oops, sorry, I didn't know this was not appropriate, first thread on HN, long time reader.