fix the project pages
This commit is contained in:
Torsten Ruger
parent
9de06bfb68
commit
22a3d42cb6
@ -1,10 +1,10 @@
|
||||
.row
|
||||
%ul.nav
|
||||
%li
|
||||
%a{:href => "/project/motivation.html"} Motivation
|
||||
%a{:href => "motivation.html"} Motivation
|
||||
%li
|
||||
%a{:href => "/project/ideas.html"} Ideas
|
||||
%a{:href => "ideas.html"} Ideas
|
||||
%li
|
||||
%a{:href => "/project/history.html"} History
|
||||
%a{:href => "history.html"} History
|
||||
%li
|
||||
%a{:href => "/project/contribute.html"} Contribute
|
||||
%a{:href => "contribute.html"} Contribute
|
||||
|
||||
@ -1,8 +1,7 @@
|
||||
%hr/
|
||||
%p
|
||||
layout: project
|
||||
title: Join the fun
|
||||
—
|
||||
= render "pages/project/menu"
|
||||
|
||||
%h1= title "Join the fun"
|
||||
|
||||
%p
|
||||
I am very open for people to join. Say hello at the
|
||||
= succeed "." do
|
||||
@ -22,27 +21,19 @@
|
||||
(on mac)
|
||||
%p I wrote some ideas in the about page, but here some more code related guidelines
|
||||
%ul
|
||||
%li
|
||||
%p
|
||||
Walk the straight line
|
||||
Or “No futureproof” 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
|
||||
%p
|
||||
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.
|
||||
%li
|
||||
%p
|
||||
Use names rightly
|
||||
or the principle of least surprise. Programming is so much naming, so if done right will lead to a
|
||||
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
|
||||
%p
|
||||
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 leads to overly small functions, calling chains that
|
||||
are difficult to understand and serve only a misundertood slogan.
|
||||
%li Walk the straight line
|
||||
Or “No futureproof” 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
|
||||
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.
|
||||
%li Use names rightly
|
||||
Or the principle of least surprise. Programming is so much naming, so if done right will lead to a
|
||||
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
|
||||
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.
|
||||
|
||||
@ -1,41 +1,37 @@
|
||||
\---
|
||||
layout: project
|
||||
title: RubyX, where it started
|
||||
\---
|
||||
.row.vspace10
|
||||
.span12.center
|
||||
%h1
|
||||
%span
|
||||
%p
|
||||
= render "pages/project/menu"
|
||||
|
||||
%h1= title "RubyX, where it started"
|
||||
|
||||
.row
|
||||
.span1
|
||||
.span10
|
||||
%p
|
||||
Torsten Ruger started this on 10.04.2014 after having read the Blue Book 20 years earlier.
|
||||
The main ideas were:
|
||||
%p
|
||||
%b> Mikrokernel
|
||||
\: The microkernel idea: anything that can be left out, should, puts a nice upper limit
|
||||
%p
|
||||
Torsten Ruger started this on 10.04.2014 after having read the Blue Book 20 years earlier.
|
||||
The main ideas were:
|
||||
%p
|
||||
%ul
|
||||
%li Mikrokernel
|
||||
The microkernel idea: anything that can be left out, should, puts a nice upper limit
|
||||
on things and at the same time provides a great cooking pot for everyone else to try out their ideas.
|
||||
%br/
|
||||
%br
|
||||
Given gems and bundler this also seems an obvious choice. I really hope to see things i hadn't even thought of.
|
||||
%br/
|
||||
= succeed ":" do
|
||||
%b Layers represent an interface, not an implementation
|
||||
%br/
|
||||
= succeed ":" do
|
||||
%b Empowerment
|
||||
%br/
|
||||
%li Layers represent an interface, not an implementation
|
||||
It is said that every problem in computing can be solved by adding another layer
|
||||
of indirection. And so we have many layers, which, when done right, help us to
|
||||
understand the system. (Read, layers are for us, not the computer)
|
||||
But implementing each layer comes with added cost, often unnecessary.
|
||||
%li Empowerment
|
||||
I like the openness of ruby. Everyone can do what and how they want.
|
||||
And change other peoples code in an easy and sensible way.
|
||||
The best ideas survive and even better ones are coming.
|
||||
Friendly competition as it were, cooperation, independent improvement all make
|
||||
ruby gems better all the time.
|
||||
%br
|
||||
But ruby itself has not benefited from this in the same way (ie by ruby developers), because it is not in ruby.
|
||||
%br/
|
||||
= succeed ":" do
|
||||
%b To get it done
|
||||
%br/
|
||||
%br
|
||||
%li To get it done
|
||||
Beats me why this hasn't been done before.
|
||||
.row
|
||||
.span12.center
|
||||
%h1
|
||||
%span Thanks
|
||||
%p This would not have happened without:
|
||||
%h1.center Thanks
|
||||
%p.center This would not have happened without:
|
||||
/ About Us
|
||||
.row
|
||||
.tripple
|
||||
@ -94,10 +90,11 @@ title: RubyX, where it started
|
||||
%b
|
||||
%a{:href => "https://github.com/cyndis/as"} As
|
||||
ended up being the starting point for the assembly layer.
|
||||
It was nice and small and produced working ARM code, which is what i wanted, as raspberry is arm.
|
||||
= succeed "got" do
|
||||
%b
|
||||
%a{:href => "https://github.com/seattlerb/wilson"} Wilson
|
||||
It was nice and small and produced working ARM code, which is what i wanted,
|
||||
as raspberry is arm.
|
||||
%b
|
||||
%a{:href => "https://github.com/seattlerb/wilson"} Wilson
|
||||
got assimilated for similar reasons, ie small and no dependencies.
|
||||
%p
|
||||
%b
|
||||
%a{:href => "http://kschiess.github.io/parslet/"} Parslet
|
||||
@ -107,11 +104,11 @@ title: RubyX, where it started
|
||||
%b
|
||||
%a{:href => "http://bundler.io/"} Bundler
|
||||
just makes you wonder how we managed before.
|
||||
Thanks to Yahuda, for starting it and Andre for making it fantastic.
|
||||
Thanks to Yahuda for starting it, and Andre for making it fantastic.
|
||||
.row
|
||||
.span12.center
|
||||
%p
|
||||
Lastly, but most importantly there is a siritual side to this too. Actually to anything i have done for at
|
||||
least 15 years, and i just mention it
|
||||
= succeed "," do
|
||||
%a{:href => "spiritual.html"} here
|
||||
%p
|
||||
Lastly, but most importantly there is a spiritual side to this too.
|
||||
Actually to anything i have done for at
|
||||
least 15 years, and i just mention it
|
||||
= succeed "," do
|
||||
%a{:href => "spiritual.html"} here
|
||||
|
||||
@ -1,8 +1,7 @@
|
||||
\---
|
||||
layout: project
|
||||
title: Effectiveness, not efficiency
|
||||
sub-title: By way of a new look at programming.
|
||||
\---
|
||||
= render "pages/project/menu"
|
||||
|
||||
%h1.center= title "Effectiveness, not efficiency"
|
||||
//# By way of a new look at programming.
|
||||
.row
|
||||
.tripple
|
||||
%h2.center Where to go
|
||||
|
||||
@ -1,9 +1,10 @@
|
||||
\---
|
||||
layout: project
|
||||
title: Ruby in Ruby
|
||||
sub-title: RubyX hopes make the the mysterious more accessible, shed light in the farthest (ruby) corners, and above all,
|
||||
%b empower you
|
||||
\---
|
||||
= render "pages/project/menu"
|
||||
|
||||
%h1= title "Ruby in Ruby"
|
||||
%p
|
||||
%span
|
||||
RubyX hopes make the the mysterious more accessible, shed light in the farthest (ruby) corners, and above all,
|
||||
%em empower you
|
||||
.row
|
||||
.tripple
|
||||
%h2.center A better tool, a better job
|
||||
@ -59,7 +60,7 @@ sub-title: RubyX hopes make the the mysterious more accessible, shed light in th
|
||||
%em
|
||||
at all.
|
||||
Only the c std library makes them look like c functions, but they are not.
|
||||
.span12
|
||||
.row
|
||||
%p.center
|
||||
%span
|
||||
%b So what does empowerment mean.
|
||||
|
||||
@ -1,9 +1,9 @@
|
||||
%hr/
|
||||
%p
|
||||
layout: project
|
||||
title: Yes, there is a spiritual side
|
||||
sub-title: It is the question that drives us
|
||||
—
|
||||
= render "pages/project/menu"
|
||||
|
||||
%h1.center= title "Yes, there is a spiritual side"
|
||||
%p.center
|
||||
%span
|
||||
It is the question that drives us
|
||||
%p
|
||||
It’s taken me a while to come out with it, but here it goes. The nice quote (got it?) has truth in it. Though we often don’t
|
||||
know what the question is and that is fine. It is the search that drives us and almost defines us as humans.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user