4 ms·

> Starting with something that is less productive to avoid a problem you might have later if you are rich doesn't seem practical to me. this is purely engineer

> Starting with something that is less productive to avoid a problem you might have later if you are rich doesn't seem practical to me. this is purely engineers' qualification issue, the fact that the hired engineers weren't productive in safer and more performant languages so they had to fallback to an inferior toolchain to seem like a productive team.

BiteCode_dev 4y ago
Simple tasks like fiddling with an API json response with rust, haskell or ocaml are always going to take longer than with python. Now, doing it well will take as much time in any language. But a huge amount of time is spent not doing things well: - you try out ideas - you explore data shape, results and systems behavior - you demos things to get a sense of the solutions or sell something to management or clients Eventually, you will have a very well defined problem with an optimal solution. But this is the last mile, unless you work for nasa. E.G: currenly one of my client is a big financial structure, and they are creating a calculation engine. They have 3 experts on site, but they don't have the full understanding of the problem they want to solve, and disagree on the part they do understand. The result ? We have to rewrite a lot of code, and write even more code in an exploratory manner. This will likely go on for the next few years. You can wish for a better situations, or you can use a tool that make you productive in that situation.
- ghostwriter 4y ago
  > Simple tasks like fiddling with an API json response with rust, haskell or ocaml are always going to take longer than with python. This isn't true, you are generalising your own perception of the tools you're not as familiar with as python. For instance, here's how simple json api fiddling looks in Haskell, if written quick-and-dirty prototyping way: -- requires packages: aeson, wreq, lens {-# LANGUAGE OverloadedStrings #-} import Network.Wreq (get, responseBody) import Data.Aeson.Lens (key) import Control.Lens main = do result <- get "http://httpbin.org/get" print (result ^. responseBody) print "---" print (result ^? responseBody . key "url") Now, how exactly is it taking longer than with Python?
polygamous_bat 4y ago
While I disagree with your "qualification issue", even that can be caused by money. Surely, hiring "more qualified" engineers cost more money that you may not have in a humble beginning.

BiteCode_dev 4y ago

Simple tasks like fiddling with an API json response with rust, haskell or ocaml are always going to take longer than with python. Now, doing it well will take as much time in any language. But a huge amount of time is spent not doing things well: - you try out ideas - you explore data shape, results and systems behavior - you demos things to get a sense of the solutions or sell something to management or clients Eventually, you will have a very well defined problem with an optimal solution. But this is the last mile, unless you work for nasa. E.G: currenly one of my client is a big financial structure, and they are creating a calculation engine. They have 3 experts on site, but they don't have the full understanding of the problem they want to solve, and disagree on the part they do understand. The result ? We have to rewrite a lot of code, and write even more code in an exploratory manner. This will likely go on for the next few years. You can wish for a better situations, or you can use a tool that make you productive in that situation.

ghostwriter 4y ago
> Simple tasks like fiddling with an API json response with rust, haskell or ocaml are always going to take longer than with python. This isn't true, you are generalising your own perception of the tools you're not as familiar with as python. For instance, here's how simple json api fiddling looks in Haskell, if written quick-and-dirty prototyping way: -- requires packages: aeson, wreq, lens {-# LANGUAGE OverloadedStrings #-} import Network.Wreq (get, responseBody) import Data.Aeson.Lens (key) import Control.Lens main = do result <- get "http://httpbin.org/get" print (result ^. responseBody) print "---" print (result ^? responseBody . key "url") Now, how exactly is it taking longer than with Python?

polygamous_bat 4y ago

While I disagree with your "qualification issue", even that can be caused by money. Surely, hiring "more qualified" engineers cost more money that you may not have in a humble beginning.