User DBlackborough

11 votes

Why is Zend Framework so complicated?

answered Dec 6, 2011 at 14:37

5 votes

Accepted

PHP framework plunge

answered May 18, 2011 at 10:40

5 votes

What are some things you have read that inspired and guided you as a programmer?

answered Oct 26, 2010 at 9:02

3 votes

How do I deal with code of bad quality contributed by a third party?

answered Feb 1, 2011 at 9:45

3 votes

Pointless Code In Your Source

answered Aug 21, 2011 at 0:42

3 votes

Why is OOP difficult?

answered Nov 1, 2010 at 14:04

3 votes

Can you successfully keep managing when you are forced back into development?

answered Dec 12, 2011 at 17:06

2 votes

Accepted

Do you store mysql exports in your version control tool for reverting to in event of error?

answered Feb 1, 2011 at 15:00

1 vote

What do you optimize for?

answered Nov 9, 2010 at 10:45

0 votes

Next step after creating mock-up screens

answered Jul 25, 2012 at 16:25

0 votes

One good reason for a rewrite

answered Feb 21, 2011 at 22:51

0 votes

Function before design, or a little of both?

answered Apr 24, 2011 at 19:31

0 votes

Stuff every programmer needs while working

answered Oct 26, 2010 at 13:43

0 votes

Which is best for learning how to do a certain thing: writing your own or looking at someone else's?

answered Oct 26, 2010 at 22:04

-1 votes

At which point do you "know" a technology enough to list it on a resume

answered Oct 27, 2010 at 11:10

Stack Exchange Network

15 Answers

Why is Zend Framework so complicated?

PHP framework plunge

What are some things you have read that inspired and guided you as a programmer?

How do I deal with code of bad quality contributed by a third party?

Pointless Code In Your Source

Why is OOP difficult?

Can you successfully keep managing when you are forced back into development?

Do you store mysql exports in your version control tool for reverting to in event of error?

What do you optimize for?

Next step after creating mock-up screens

One good reason for a rewrite

Function before design, or a little of both?

Stuff every programmer needs while working

Which is best for learning how to do a certain thing: writing your own or looking at someone else's?

At which point do you "know" a technology enough to list it on a resume