pottereric

7 ms·

1.
by pottereric 7mo ago
Cool animations. Does anyone know how they made those animations? Or did they do it with vanilla JS/CSS/HTML?
2.
Zone of Ceremony(blog.ploeh.dk)
1 points by pottereric 7y ago|0 comments
3.
The Kranz Dictum: An excellent example of effective leadership in action(jarango.com)
2 points by pottereric 7y ago|0 comments
4.
Thriving on the Technical Leadership Path(keavy.com)
3 points by pottereric 7y ago|0 comments
5.
Introduction to the Model View Update Pattern(elmprogramming.com)
1 points by pottereric 7y ago|0 comments
6.
On Focus (2018)(dennisdel.com)
22 points by pottereric 7y ago|2 comments
7.
Internet-era ways of working(public.digital)
1 points by pottereric 8y ago|0 comments
8.
On Focus (2018)(dennisdel.com)
2 points by pottereric 8y ago|0 comments
9.
Against metrics: how measuring performance by numbers backfires(aeon.co)
2 points by pottereric 8y ago|0 comments
10.
The 'Coffee Shop Effect': Why Changing Your Location Boosts Your Productivity(blog.trello.com)
3 points by pottereric 8y ago|0 comments
11.
Maker vs. Manager: How Your Schedule Can Make or Break You(fs.blog)
2 points by pottereric 9y ago|0 comments
12.
Psychological Safety, Risk Tolerance and High Functioning Software Teams(medium.com)
2 points by pottereric 9y ago|0 comments
13.
Observations about StackOverflow's most disliked languages(blog.apterainc.com)
1 points by pottereric 9y ago|0 comments
14.
GTOP – System monitoring dashboard for terminal(github.com)
1 points by pottereric 9y ago|0 comments
15.
by pottereric 9y ago
It is a problem I've seen in the real world. For example, I've seen a project where upper management tasked a team of developers with writing software and didn't give the team specific direction nor did they communicate clear
16.
by pottereric 9y ago
> This author starts with the implicit premise that change is bad and all conclusions are the result of that. How did you come to that conclusion? The theme of what I was saying is that projects to be given direction from the stakeholder
17.
Salmon-ladder development is not the way to do agile(blog.apterainc.com)
19 points by pottereric 9y ago|20 comments
18.
Software Rockstars? Really?(blog.apterainc.com)
2 points by pottereric 9y ago|0 comments
19.
The MVP is dead. Long live the RAT(medium.com)
2 points by pottereric 10y ago|0 comments
20.
by pottereric 10y ago
Forgive my ignorance. What do Rust and Go call their data structures that are analogous to classes?
21.
by pottereric 10y ago
I agree with you in that I don't agree with the author. I felt that the strongest point of the paper was that it was critical of something that is assumed to be a good thing. That value was that it challenged one of my assumptions that
22.
Classes Considered Harmful [pdf](web.cecs.pdx.edu)
135 points by pottereric 10y ago|125 comments
23.
Productivity Patterns(leadingagile.com)
2 points by pottereric 10y ago|0 comments
24.
The Path to Craftsmanship and the Art of Being Wrong(hackaday.com)
1 points by pottereric 10y ago|0 comments
25.
On Finding Learning(blogs.tedneward.com)
1 points by pottereric 10y ago|0 comments
26.
Team Learning as Team Building(blog.apterainc.com)
1 points by pottereric 10y ago|0 comments
27.
I’m a boring programmer (and proud of it)(m.signalvnoise.com)
11 points by pottereric 10y ago|1 comments
28.
Is Programming Art?(daedtech.com)
2 points by pottereric 11y ago|0 comments
29.
Tim Ferriss and the Secrets of Accelerated Learning(forbes.com)
2 points by pottereric 11y ago|0 comments
30.
The Illogical Allure of Extremes(medium.com)
1 points by pottereric 11y ago|0 comments

More ›