Best practices in modern web projects
blog.arvidandersson.se
Best practices in modern web projects
1–10 of 89 posts
Re: Best practices in modern web projects
#2All of this really covers the primary thing I preach when working with new devs. "You shouldn't be the only one who knows how to set this up and run it."
One thing that might be missing is good code documentation. Using DocBlock for PHP, for example. Ideally this is maintained in code, but that can get bloaty. At the very least, a git repo of markdown files. Even the built-in github wikis would suffice.
Re: Best practices in modern web projects
#3These aren't really best practices, they're too abstract. Best practices would be exactly how you do said practices the best way possible.
A more appropriate title could be "list of must read articles for modern web development".
Re: Best practices in modern web projects
#4"Git
First of all, use git for version control. It is modern, works great and the majority of developers are either comfortable in using it or want to start using it.
Its a pain in the arse to learn, overcomplicated for 90% of the cases it is used in. How many people actually need a distributed version control."
(I use Git. It is powerful and useful, but the justification for using it in the article isn't really great. No mention of Mercurial or other version control systems).
Re: Best practices in modern web projects
#5These aren't really best practices, they're too abstract. Best practices would be exactly how you do said practices the best way possible. A more appropriate title could be "list of must read articles for modern web development".
I'm not sure about that; I feel like I got a lot from the article without following the links.
Re: Best practices in modern web projects
#6"Git First of all, use git for version control. It is modern, works great and the majority of developers are either comfortable in using it or want to start using it. Its a pain in the arse to learn, overcomplicated for 90% of the cases it is used in. How many people actually need a distributed version control." (I use Git. It is powerful and useful, but the justification for using it in the article isn't really grea…
The benefit of standardizing on a tool that is "good enough" is worth it imo. Learning git is easier than learning svn, darcs, hg, perforce and git and juggling between them when you want to submit patches to open source projects or get new clients.
Re: Best practices in modern web projects
#7"Git First of all, use git for version control. It is modern, works great and the majority of developers are either comfortable in using it or want to start using it. Its a pain in the arse to learn, overcomplicated for 90% of the cases it is used in. How many people actually need a distributed version control." (I use Git. It is powerful and useful, but the justification for using it in the article isn't really grea…
The world's inconsistent internet connections are a great reason to require distributed version control. I'm often trying to work from a location without a reliable connection to the internet, be it a plane, train or bus, a coffee shop with spotty internet or a meetup. Requiring a connection to a server kills productivity in those situations.
Perhaps there is something to be said for Mercurial, but unless you were previously on Subversion it's certainly not that it's easy to learn.
Re: Best practices in modern web projects
#8"Git First of all, use git for version control. It is modern, works great and the majority of developers are either comfortable in using it or want to start using it. Its a pain in the arse to learn, overcomplicated for 90% of the cases it is used in. How many people actually need a distributed version control." (I use Git. It is powerful and useful, but the justification for using it in the article isn't really grea…
The benefit of standardizing on a tool that is "good enough" is worth it imo. Learning git is easier than learning svn, darcs, hg, perforce and git and juggling between them when you want to submit patches to open source projects or get new clients.
Don't forget bzr!
Re: Best practices in modern web projects
#9No idea how this is getting so many points. There's absolutely nothing of any practical interest here. Use version control and documentation... End of post. I'd say these are more industry standard practices than leading edge.
Re: Best practices in modern web projects
#10These aren't really best practices, they're too abstract. Best practices would be exactly how you do said practices the best way possible. A more appropriate title could be "list of must read articles for modern web development".
I'm not sure about that; I feel like I got a lot from the article without following the links.
[deleted]