3 ms·
(The last time I worked on a Prolog program was 20 years ago. It had only around 4000 lines, so take the following with a grain of salt.) For me, a work day in
by tralarpa 8y ago
(The last time I worked on a Prolog program was 20 years ago. It had only around 4000 lines, so take the following with a grain of salt.)
For me, a work day in Prolog looked like this: Write your idea down in 1 hour and then spend the remaining 7 hours figuring out where to place the cuts :)
- marmaduke 8y agoSometimes I think my Python code has 7 lines of validation or plumbing for each line of algorithm.
- jgalt212 8y agonot far from the truth, but I guess it comes down to where to you place the technical debt (up front with statically typed langues), or after you have something working (dynamic languages). I favor the later because of the low cost of experimentation, but you do need get around to hardening the system, and that part has real costs.
- taeric 8y agoWhile i agree with the technical debt here, I think you slightly misplace it. You take debt by using the libraries available on python. Same as you take loans from others that have capital. The currency here is their knowledge. That is, the dynamic/static divide is a distraction. Easy to talk towards, but likely nowhere near as important as other factors.
- marmaduke 8y agoIt has nothing to do with technical debt or typing but that input data could violate assumptions of the algorithm. Duck typing and Python large ecosystem does tend to exacerbate that though