Thank you for the insight, well written, simple and pragmatic thoughts those you have shared with us.
And Adrian comment was the cherry on top of the cake. Thank you also for your shares.
After 15 years of sysadmin, I've fall in love again with my academic passion - programming (back then it was mainly C and LISP).
15y later got back to the books... a bit of everything - Software Engineering, DB engineering, UML, RUP, Agile, CVS, php MVC frameworks, etc and found myself fascinated with this new world of WebAPP development. Finally I felt good at my job and found happiness as a professional :)
But being also a perfectionist bitch (btw good to know I'm not the only "bitch" around) all the avalanche of info and knowledge soon became a block element, just like you posted. Your two steps make perfect sense to me.
Until now, my apps GUI are also zero JS pretty much the same way and with the same intuit as Adrian, waiting for the jquery d-day to take better care of UI.
One other thing I do is break up my CSS in 2-3 or 4 parts that match the agile development phases, it helps me to understand my layouts and debug them also. Until their ready to become just 1 css file.
To finish my first turnkey user comment, I would like to ear your thoughts regarding code optimization development (sql instructions included). Should I consider it a third block element?
I never know when it's time to stop everything and focus on those lines that cost me 100 cpu cycles and refurbish them to achieve same results in 20 cycles. No one will notice those 50ms gain but seems like those lines can't get away my perfectionist-bitch-sourcecode-sight.
You've just deepened my existing paths
Thank you for the insight, well written, simple and pragmatic thoughts those you have shared with us.
And Adrian comment was the cherry on top of the cake. Thank you also for your shares.
After 15 years of sysadmin, I've fall in love again with my academic passion - programming (back then it was mainly C and LISP).
15y later got back to the books... a bit of everything - Software Engineering, DB engineering, UML, RUP, Agile, CVS, php MVC frameworks, etc and found myself fascinated with this new world of WebAPP development. Finally I felt good at my job and found happiness as a professional :)
But being also a perfectionist bitch (btw good to know I'm not the only "bitch" around) all the avalanche of info and knowledge soon became a block element, just like you posted. Your two steps make perfect sense to me.
Until now, my apps GUI are also zero JS pretty much the same way and with the same intuit as Adrian, waiting for the jquery d-day to take better care of UI.
One other thing I do is break up my CSS in 2-3 or 4 parts that match the agile development phases, it helps me to understand my layouts and debug them also. Until their ready to become just 1 css file.
To finish my first turnkey user comment, I would like to ear your thoughts regarding code optimization development (sql instructions included). Should I consider it a third block element?
I never know when it's time to stop everything and focus on those lines that cost me 100 cpu cycles and refurbish them to achieve same results in 20 cycles. No one will notice those 50ms gain but seems like those lines can't get away my perfectionist-bitch-sourcecode-sight.
Again, thank you for the enjoyable reading
Nuno