lukesan

6 ms·

1.
by lukesan 10y ago
Take a look at the works of Nicholas Felton http://feltron.com/ especially his reports of his years of personal data like http://feltron.com/FAR09.html These might give you ideas.
2.
Show HN: I made a zine for the modern developer (issue 1: CQRS)(schneide.wordpress.com)
4 points by lukesan 10y ago|0 comments
3.
Getting better at programming without coding(schneide.wordpress.com)
6 points by lukesan 10y ago|0 comments
4.
What I've learned in UX in the first half of 2016(schneide.wordpress.com)
2 points by lukesan 10y ago|0 comments
5.
by lukesan 10y ago
Simplicity is overrated. Experts often need more than the simple mantra 'do one thing well'. What is often needed for the user (novices and experts) is clarity. An unambiguous, clear interface is much better than a simple one. Eve
6.
by lukesan 10y ago
Thanks a lot.
7.
by lukesan 10y ago
Thank you for taking time and the effort to response. I appreciate that. I agree with the notion that you need to be free in choosing what you want to build. I like the notion of why, what, how in http://abbytheia.com/2016&#
8.
by lukesan 10y ago
"maybe we can get away with X", or "maybe this will be good enough" I think it is important to ponder about what is the best (efficient, best matching, ...) solution to the problems the user has. In your definition agili
9.
Requirements should not drive development(schneide.wordpress.com)
1 points by lukesan 10y ago|0 comments
10.
The high price of free(alistapart.com)
1 points by lukesan 11y ago|0 comments
11.
by lukesan 11y ago
Sounds great. Do you know any good resources for building a react application by progressive enhancement?
12.
by lukesan 11y ago
What really bothers me about React (and other frameworks) that without JS you do not see anything. No fallback. No progressive enhancement. Is this really the way to go? Did JS replace HTML/CSS as the backbone of websites/applicat
13.
Beyond agile: building on the roots(schneide.wordpress.com)
1 points by lukesan 11y ago|0 comments
14.
Learning UX design: where do I start(schneide.wordpress.com)
1 points by lukesan 11y ago|1 comments
15.
Thinking in immutability(schneide.wordpress.com)
2 points by lukesan 11y ago|0 comments
16.
Universal skills every software developer can benefit from(schneide.wordpress.com)
3 points by lukesan 11y ago|0 comments
17.
Don't Delete – Just Don't (2009)(udidahan.com)
1 points by lukesan 11y ago|0 comments
18.
Software development is code organization(schneide.wordpress.com)
4 points by lukesan 11y ago|1 comments
19.
Assumptions – how to find, track and eliminate them(schneide.wordpress.com)
1 points by lukesan 11y ago|0 comments
20.
The web is for documents(schneide.wordpress.com)
1 points by lukesan 11y ago|0 comments
21.
by lukesan 11y ago
But as with other things based on taste: the perception matters most, not a scientific double blind study. If my perception makes me prefer one coffee over the other, I am happy.
22.
by lukesan 11y ago
"To clarify, add detail" - E. Tufte I don't think reduction only leads to perfection. If it would be, then our starting point must always be the right one. But in practice you start somewhere, reduce, move forward, add stuff,
23.
The typography of source code(schneide.wordpress.com)
4 points by lukesan 11y ago|0 comments
24.
by lukesan 11y ago
Yes, in an iterative way. Maybe it is also agile :)
25.
Transparent software: making complexity understandable(schneide.wordpress.com)
2 points by lukesan 11y ago|0 comments
26.
What developers can learn from designers(schneide.wordpress.com)
2 points by lukesan 12y ago|0 comments
27.
by lukesan 12y ago
>What we really do is assess the validity and feasibility of what an user wants Then why do software developers get no training in talking to users? In understanding them and make sense of what they tell us and what they really? This to
28.
I am learning to write better software(betteruxdesign.wordpress.com)
1 points by lukesan 12y ago|0 comments
29.
by lukesan 12y ago
I would start with Refactoring by Martin Fowler. For me this is the quintessential book when it comes to basic software design principles. It introduces code smells and tells you step by step how and why to improve your code design
30.
Web, your users deserve better(schneide.wordpress.com)
1 points by lukesan 12y ago|0 comments

More ›