LukaAl

15 ms·

121.
by LukaAl 11y ago
It is actually a cost and Walker is wrong. What changes is how the cost is spread. If you buy a building and you spend 1M you will have -1M cash and +1M in property. But since the building will age you will have to amortize it, let's s
122.
by LukaAl 11y ago
The observation on failure modes is correct. When you process thousands of tasks every day even problems with low probability happens. What bugs me with the transaction approach is that you loose all the information (except probably for log
123.
by LukaAl 11y ago
Thanks for the article, very interesting. Just one point on the solution. To my understanding, you prefer a queue implemented on a DB because transactions guarantee that a task could not start unless the task before as succeeded and committ
124.
by LukaAl 11y ago
There are many problems in this article. The biggest problem I see is in the value of an iPhone and in the capital that is locked while it is in transit. Although there is little information on Apple's operation, a quick look at their
125.
by LukaAl 11y ago
First of all, I'm not totally sure a huge seller like Foxconn has less negotiating power with logistics company than Apple (actually is probably higher). Then, Apple could negotiate the logistics but still account the merchandise as FO
126.
by LukaAl 12y ago
Ok, now also the Mac version is twittable: echo 'const int main[]={1208,114434,2370306048,2101,834048,84869120,1818577091,1461743468,1684828783,10};'|cc -xc -ot -&&./t The trick is to use retq instead of a sys
127.
by LukaAl 12y ago
echo 'const int main[]={3850979413,184,3234285568,33554436,29869896,1207959552,1652109,3343384576,3522,1208291072,114887,3343385088,199,1208291072,1869376613,1919899424,169960556};'>t.c&&gcc t.c&&./a.o
128.
by LukaAl 12y ago
Agree on the need of powerful tool. And sometimes you ends up spending time writing the right tool for that specific tasks when it is missing (done more than one time). On your rebuttal on the tools for established industries, I just said t
129.
by LukaAl 12y ago
I use coder because that's the term used in the question. I prefer software engineer usually. I'm not a coder, or software engineer, for what it matters but I'm doing it now and I understand how it works and I use all sort of
130.
by LukaAl 12y ago
What do you mean for "writing tools as powerful as those used by coders"? In my experience good coders doesn't need very powerful tool. Super-complex IDE are usually a disturbance to good coders rather then an help and even t
131.
by LukaAl 12y ago
What do you mean by backlog depends a lot on what you are selling: - If it is software, usually you sells it in stage or you have to deliver customization/integration at a later stage: - If it is SaaS is like before but you have also t
132.
by LukaAl 12y ago
I've been a manager working for telco companies so I know a bit about it. Usually the backlog is a good metric but it works from when you have already sold the product. Usually to assess what happens before the sales team is asked to a