rumcajz

60 ms·

571.
by rumcajz 12y ago
There's -fsplit-stack option in gcc IIRC.
572.
Coroutines in C with Arbitrary Arguments(250bpm.com)
62 points by rumcajz 12y ago|22 comments
573.
by rumcajz 12y ago
I think this is going to get important economically. There's only limited amount of resources a person can consume for consuming sake. The rest is conspicuous consumption (buying a Ferrari to improve your social status) or its watered
574.
by rumcajz 12y ago
Speaking as an author of one of the articles in AOSA: What would you write if you were the author? Software architecture is very much just a bag of tips and tricks and rules of thumb. The result is, not surprisingly, pretty disparate.
575.
by rumcajz 12y ago
Nanomsg API is crafted in such a way as to allow for network-level zero-copy. This is much unlike other messaging products. However, I know of no implementation that actually uses that.
576.
by rumcajz 12y ago
To decide whether to optimise/not optimise or use goto/avoid goto you need some amount of experience. Thus, people with no such experience resort to the rules of thumb (don't optimise, don't use gotos). From there it&#x2
577.
by rumcajz 12y ago
Rarely (unless you are working on your hobby project) you get a chance to make program simple. There are inherently complex requirements that can't be changed for political reasons, complex legacy interfaces to conform to et c. Interes
578.
A cryptopuzzle. Ready, steady, go(250bpm.com)
1 points by rumcajz 12y ago|0 comments
579.
by rumcajz 12y ago
Rule of 3 should apply to interfaces. Don't make an interface unless there are at least 3 implementations.
580.
by rumcajz 12y ago
What you typically do is work remote and meet in person once in a (long) while. This is how lot of open source projects work.
581.
by rumcajz 12y ago
Having experienced different setups, it seems that collaboration is OK if everyone is at the same place. It's also OK is everyone is remote. Where it gets troublesome is when part of the team is collocated and part is remote. What you
582.
by rumcajz 12y ago
I've wrote down some thoughts on possible economics of "bullshit jobs" here: http://250bpm.com/blog:44 Here's the relevant part of it: "Can we do the same trick here and stop thinking about competin
583.
by rumcajz 12y ago
It also has to do with the fact that programmers are often ignorant about the problem domain and frequently don't even try to understand it. That makes them unable to solve the domain problems. They just follow the spec written by busi
584.
by rumcajz 12y ago
C devs are OK with working with a 40 years old technology. Actually, they are happy that it doesn't change every 6 months.
585.
by rumcajz 12y ago
Good write-up. I've been observing this phenomenon for years and I think that one of the main causes is poor cost estimation by developers (or, often, no cost estimation). The new project lead asks management to allow him to re-write t
586.
The Lava Layer Anti-Pattern(mikehadlow.blogspot.com)
181 points by rumcajz 12y ago|76 comments
587.
CIA agents who tortured are vulnerable to prosecution in any country(amanpour.blogs.cnn.com)
221 points by rumcajz 12y ago|133 comments
588.
by rumcajz 12y ago
I wonder what would happen if they've required the ISPs to give better service to the content provided by German companies.
589.
by rumcajz 12y ago
No, I don't have statistical data, but I've experienced both sides in person. The crucial difference is sensitivity to ROI. When not paid, every hour spent programming is an hour not spent with your family, not spent attending to
590.
by rumcajz 12y ago
Not being paid is integral part of open source development. It keeps the incentives to produce quality, lean code straight.
591.
Non-interactive zero knowledge proofs for fun and profit(250bpm.com)
2 points by rumcajz 12y ago|0 comments
592.
by rumcajz 12y ago
It's more of a declarative language. Like Prolog.
593.
by rumcajz 12y ago
The interesting part is that recruiters seem more in agreement when identifying low performers. When faced with a high performer their scores differ wildly.
594.
by rumcajz 12y ago
Well, what I wanted to say was that the "craft", i.e. skills learned when working on a real project with experienced developers, is something I use all the time. Academic knowledge less so. Take, for example, complexity theory. I
595.
by rumcajz 12y ago
Programmers are craftsmen. They need vocational schools. Academia is not up to the job.
596.
by rumcajz 12y ago
Alan Kay may have coined the term, but OOP (as any other word or term) is what people believe it to be. Which is pretty far from CSP.
597.
by rumcajz 12y ago
I've done a little write-up on the sociology/economics of the work done beyond what's actually useful: http://250bpm.com/blog:44
598.
The Clockwork inside Game of Thrones(250bpm.com)
1 points by rumcajz 12y ago|0 comments
599.
Bullshit jobs(250bpm.com)
1 points by rumcajz 12y ago|0 comments
600.
Magic numbers in C(250bpm.com)
2 points by rumcajz 12y ago|0 comments

More ›