Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
4 9
~14k people reached

  • 0 posts edited
  • 0 helpful flags
  • 23 votes cast
comment What advantages are conferred by using server-side page rendering?
Isn't one factor also potential scalability? If you are rendering 1000s of pageviews/second, surely it's more scalable to render those on the client-side rather than the server-side?
comment Submitting software to a competition, it becomes their property?
@Philip I disagree. I've updated my answer accordingly.
comment Why not write all tests at once when doing TDD?
@maple_shaft I think that was what Jeff O was getting at with his comment, no?
comment I'm going to quit my job because of our platform: how can I leave a productive explanation of this?
+1 for waiting till you get another job. Doesn't matter what you are doing, you're infinitely more employable if you are currently in work!
comment Creating database connections - Do it once or for each query?
@briddums - I think that depends on the connector. .Net, for example, doesn't provide a MySql connector. It's written and maintained by MySql. And whilst it works, in my experience the earlier implementation were far from bug free.
comment Single-developer GIT workflow (moving from straightforward FTP)
Yes, that's basically it. In fact I use Subversion. We have sites on Windows as well as Linux servers. On Windows I remote desktop onto them, make the CSS change and commit using TortoiseSVN. On Linux I use an SSH session and vim to make the changes (but you can also FTP your changes I guess).
comment Single-developer GIT workflow (moving from straightforward FTP)
For a minor CSS change I would make the change directly on the server and then commit that change to the repository from the server. When I have to do a more serious amount of work on the site I would then update the site on my dev machine with the latest version of the site from the repository. I guess it doesn't really matter where you make the change (server or dev machine) as long as you commit it to the repository.
comment “Don't do programming after a few years of starting career”. Is this a fair advice?
@KeithS. I can't help feeling this is the true difference between good and poor programmers. It's not the quality of the code they produce. It's whether what they produce actually solves the client's problem.
comment Not getting paid for hours you've worked?
Is it possible to be truly productive for 80 hours in a week? I think not. By the 70th hour you are probably adding more bugs than you are fixing, or at the very least introducing more technical debt. Companies expecting you to routinely work 80 hour weeks (for months on end) are likely to fail due to shoddy software created either by tired developers or high developer turnover.