jakubholynet

6 ms·

1.
Avoiding Yak Shaving – Focus and Do the Simplest Thing Possible(blog.iterate.no)
2 points by jakubholynet 12y ago|0 comments
2.
Seeking A Better Alternative To Interrelated Mutable Fields(wondersofcode.wordpress.com)
2 points by jakubholynet 13y ago|0 comments
3.
Webapp Blue-Green Deployment Without Breaking Sessions/With Fallback W/ HAProxy(theholyjava.wordpress.com)
2 points by jakubholynet 13y ago|0 comments
4.
Straightforward vs. Structured, Non-repetitive Code: Which Would You Choose?(wondersofcode.wordpress.com)
1 points by jakubholynet 13y ago|0 comments
5.
by jakubholynet 13y ago
Well, in Norway nearly everybody uses "Scrum" but Scrum is not always Scrum. To make it rock, you need a certain mindset - in the team and the company - and culture. It is primarily about values and culture, not processes. Changing culture
6.
by jakubholynet 13y ago
I would be coding for fun :-) Working in languages and toolchains of my choice (Clojure, f.ex.), helping organizations worth helping (NGOs,...). But that would be only a part-time activity, I would use the other part for stuff I like &
7.
by jakubholynet 13y ago
You are right, we all do this. What is missing from this is feedback: how do I know if my design is good enough or what are its pros & cons? (Since often there is no absolute "good".) That is something I am trying to provide: showing tw
8.
by jakubholynet 13y ago
Thank you, bjoerns! That is actually a good suggestion and modern screens are wide enough for that. I am afraid that Wordpress won't allow me to do that but will explore it.
9.
Good/Bad Code Study: Method Promiscuity Or The Case For Encapsulation (Python)(wondersofcode.wordpress.com)
1 points by jakubholynet 13y ago|0 comments
10.
Can we become better programmers through studying code?
5 points by jakubholynet 13y ago|8 comments
11.
Good/Bad Code Study: Simple x Easy: Writing A Generic Code To Avoid Duplication(wondersofcode.wordpress.com)
1 points by jakubholynet 13y ago|0 comments
12.
Bad Code: Too Many Object Conversions Between Application Layers(wondersofcode.wordpress.com)
6 points by jakubholynet 13y ago|0 comments
13.
Good/Bad Code Study: Intention Hidden In Implementation, Misty Edge of Validity(wondersofcode.wordpress.com)
2 points by jakubholynet 13y ago|0 comments
14.
by jakubholynet 14y ago
> - Assign a career mentor > - Devise and maintain a career development plan for each prospect These are great advices. The question is how to turn them into practice. People do not become great mentors by just becoming appointed :
15.
by jakubholynet 14y ago
I agree there is much more stuff than writing code. > Teaching them the value of well organized source control and good commit notes goes a long way. This is way too low level compared to what we are looking for. We want to find out how
16.
by jakubholynet 14y ago
> Give them real life projects that you will use. We do that. But we feel it is not enough to help people grow quickly. We are looking for ways to make the learning process as effective as possible.
17.
by jakubholynet 14y ago
Some of the new stuff is mentioned at http://www.joyofclojure.com/2nd - - ClojureScript - more on "thinking" techniques, f.ex. unification, logic programming, constraint solving, declarative programming - Data-orientation: "dive deeply
18.
by jakubholynet 14y ago
We use Guice which also allows that. But that doesn't address some of the key points he makes, such as - runtime x compile time wiring - wiring is based on types so injecting differently set up instances is difficult (we have a hell of Pro
19.
The Sprinting Centipede Strategy: How to Improve Software Without Breaking It(blog.iterate.no)
2 points by jakubholynet 14y ago|0 comments
20.
by jakubholynet 14y ago
Sorry but to me this hears similarly too "coders do not care about why runtime speed is slow, they just want it fast". You cannot get gut runtime performance without understanding the performance constraints of data structures and algorithm
21.
Fast Code To Production Cycle Matters: For Pleasure, Productivity, Profit(theholyjava.wordpress.com)
1 points by jakubholynet 14y ago|0 comments
22.
by jakubholynet 14y ago
PhatnomJS and Buster really seem to be the cool kids. I hope to see more tests of front-end code integrated in Jenkins & similar ones soon.
23.
by jakubholynet 14y ago
Hi Jacques, Thank you for your comment, I thoroughly enjoyed it. Thank you also for summarizing the many forseeable possible discussions upfront so that we could have avoided them here. The books were chosen by a group of five, half of us w
24.
by jakubholynet 14y ago
Sounds interesting, good luck! Thread switching is certainly costly and not really necessary for high-performance systems as proved by the the LMAX/Disruptor architecture.
25.
Minimalistic Practical Introduction to Puppet (Not Only) For Vagrant Users(theholyjava.wordpress.com)
1 points by jakubholynet 14y ago|0 comments