Summary; I don't like frameworks, so I rolled my own framework.
A friend of mine does software consulting for medical groups. He rolled his own framework which is a combination of SQL Server and ASP classic. The funny thing is that it was the SQL Server stored procedures that generated the HTML, not ASP. I couldn't figure out if it was genius or insane.
How I Build PHP Applications
51–56 of 56 posts
Re: How I Build PHP Applications
#52Earlier quoted context omitted.
Why carry around the weight of a framework if you're happier doing things this way? Insofar as an idea on putting together a sane PHP project built from the ground up, I think it's a good article.
What 'weight'? A good framework doesn't stand in your way, it lets u focus on business logic solutions instead of repeatable tasks. Sooner or later he'll discover that he's getting to the point where he needs to provide solutions for problems that are already solved by a variety of well-maintained toolsets, and the lack of abstraction will make his projects hard to develop further.
Re: How I Build PHP Applications
#53Summary; I don't like frameworks, so I rolled my own framework.
I think it is more accurate to say he wrote his own library. These terms are not well defined (AFAIK) but often a framework implies that you have something “already running” which you customize by providing callbacks, delegates, and similar. With a library you have a set of reusable functions and data types (classes). I think an Apple engineer referred to frameworks as “the hollywood model: don’t call us, we call you…
Libraries, OTOH, don't presume anything about taking control. You're still the driver, they just have a lot of things that can make your life easier if you choose to use them.
Re: How I Build PHP Applications
#54Earlier quoted context omitted.
Why carry around the weight of a framework if you're happier doing things this way? Insofar as an idea on putting together a sane PHP project built from the ground up, I think it's a good article.
What 'weight'? A good framework doesn't stand in your way, it lets u focus on business logic solutions instead of repeatable tasks. Sooner or later he'll discover that he's getting to the point where he needs to provide solutions for problems that are already solved by a variety of well-maintained toolsets, and the lack of abstraction will make his projects hard to develop further.
Re: How I Build PHP Applications
#55Earlier quoted context omitted.
What 'weight'? A good framework doesn't stand in your way, it lets u focus on business logic solutions instead of repeatable tasks. Sooner or later he'll discover that he's getting to the point where he needs to provide solutions for problems that are already solved by a variety of well-maintained toolsets, and the lack of abstraction will make his projects hard to develop further.
I never would have dreamed that I'd ever see someone on Hacker News type out English's second person personal pronoun as "u".
Re: How I Build PHP Applications
#56Earlier quoted context omitted.
The big secret is that programmers make more money when they stop pitching themselves as programmers and start pitching themselves as skilled professionals who make their firms millions using a variety of tools, including code (when appropriate). OK, it isn't much of a secret. I wince every time I hear someone describe himself as a "PHP coder" in mixed company (i.e. in front of folks with hiring authority rather than…
Soooo what's your job title? It sounds like you've sugar coated the hell out of it.