ruby-x/ruby-x.github.io
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

better blog index and fix news link

Browse Source
This commit is contained in:
Torsten Ruger
2018-04-11 17:32:38 +03:00
parent 22a3d42cb6
commit 90fc084fca
4 changed files with 28 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
app/views/pages/project/contribute.html.haml
View File

@ -5,7 +5,7 @@
%p
I am very open for people to join. Say hello at the
= succeed "." do
%a{:href => "https://groups.google.com/forum/#!forum/ruby-x"} list
=ext_link "list" , "https://groups.google.com/forum/#!forum/ruby-x"
%p
I just want to mention that this is my hobby, something i do in my spare time, for fun.
I don’t get any money and in fact, running 2 companies, have to carve the time to do this.
@ -17,14 +17,14 @@
%p Then fork and work on a branch before sending pull request.
%p
If you don’t have an arm, here are instructions to run an
%a{:href => "/qemu.html"} emulator
=link_to "emulator", "/qemu.html"
(on mac)
%p I wrote some ideas in the about page, but here some more code related guidelines
%ul
%li Walk the straight line
Or “No futureproof” means not to design before you code. Not to anticipate, only to do the job that
Or “No future-proof” means not to design before you code. Not to anticipate, only to do the job that
needs doing. Better design should be extracted from working code.
%li tdd extreme
%li TDD extreme
Having suffered from broken software (small feature add breaks whole software) so many times, the new tdd
wind is not just nice, it is essential. Software size is measured in tests passed, not lines written. Any
new feature is only accepted with enough tests, bugs fixed after a failed test is written.
@ -33,7 +33,7 @@
natural understanding, even of code not read.
Good names are Formatter or compile, but unfortunately not everything we have learnt is named well, like
Array (should be ordered list), Hash (names implementation not function) or string (should be word, or bytebuffer).
%li No sahara
%li No Sahara
There has been much misunderstood talk about drying things up. Dry is good, but was never meant for code, but
for information (configuration). Trying to dry code completely leads to overly interdependent functions,
calling chains that are difficult to understand and serve only a misunderstood slogan.