vrybas1

vrybas1 on Hacker News

Work-In-Progress Pull Requests

Posted by vrybas1 on Monday September 01, 2014 @10:35AM
from the vrybas.github.io dept.

http://vrybas.github.io/blog/2014/04/11/wip-pull-requests/

( Read More... | no comments | on HN )

A Way to Organize POROs in Rails

Posted by vrybas1 on Monday August 18, 2014 @12:10AM
from the vrybas.github.io dept.

http://vrybas.github.io/blog/2014/08/15/a-way-to-organize-poros-in-rails/

( Read More... | no comments | 2 points | on HN )

Re:Source code for the Apollo 11 Guidance Computer on Tuesday July 22, 2014 @12:12AM (#8067358)

Story behind the code:

TALES FROM THE LUNAR MODULE GUIDANCE COMPUTER http://www.doneyles.com/LM/Tales.html

Re:Optimize for readability first. What slows down developers when rea... on Wednesday July 09, 2014 @08:23AM (#8009244)

I'm getting closer & closer to make this statement a rule:

"Code need to be that good - no one in a team can write any better"

If you, knowing current requirements, wrote a perfect code - it will still become messy at some point. Feature by feature new things will appear here and there. Functions size will grow, this CASE statement will grow etc. But still the "core" of it will be strong.

If you, knowing current requirements, deliberately wrote a "good enough" code, what will happen with next change? The code won't survive it and will be deleted(at best case). Therefore, bad code is completely useless from the start.

Re:How not to write an API on Sunday March 09, 2014 @07:56PM (#7370549)

↑ This!