pederbl

4 ms·

1.
The 10 Greatest B2B SaaS Sales Pitches(medium.com)
1 points by pederbl 5y ago|0 comments
2.
How to upgrade your brain through extreme reflection(linderacademy.com)
3 points by pederbl 11y ago|0 comments
3.
Changing the Future of Higher Education(medium.com)
2 points by pederbl 12y ago|0 comments
4.
The 4 Steps To Learning Effectively from Your Actions(medium.com)
1 points by pederbl 12y ago|0 comments
5.
4 Steps to Giving Better Feedback(medium.com)
2 points by pederbl 12y ago|0 comments
6.
Boost Your Personal Development Systematically(medium.com)
1 points by pederbl 12y ago|0 comments
7.
A New Reality for HR and Managers(medium.com)
1 points by pederbl 12y ago|0 comments
8.
by pederbl 14y ago
The main problem with top-down programming that I have understood is that it tends to lead to non-DRY code (i.e. functions repeat the same logic and patterns). I have noticed that my code becomes much more DRY with this new approach because
9.
by pederbl 14y ago
What do you mean by top-down? I'd say it encourages bottom-up programming since scoped functions are so light weight. Scoped functions can easily be made global when it makes sense to share the logic.
10.
by pederbl 14y ago
Variables are one of the worst enemies to readability. Because of them a reader often can't understand a line of code without looking at lots of other lines of code to figure out what the meaning of a variable actually is. If scoped functio
11.
by pederbl 14y ago
I'm not taking a stance on whether significant whitespace is better or worse than the alternative. I'd consider swapping the {} for where ... end which would make more sense and is more similar to Haskell
12.
by pederbl 14y ago
It seems you missed my point that defining none scoped functions pollute the namespace. They also tend to drive the developer to be too generic for the specific usage that is needed. Scoped functions can be customized both in name and funct
13.
Idea for new readable code language (gist.github.com)
1 points by pederbl 14y ago|12 comments