3 ms·

I say good. One of the next tasks I'm going to take, as soon as I get some free time, is to integrate TypeScript into our front-end and start adding in interfa

by douche 10y ago

I say good. One of the next tasks I'm going to take, as soon as I get some free time, is to integrate TypeScript into our front-end and start adding in interfaces and parameter types. I'm usually working on the back-end, but get drafted into the UI-side once in a while. The number of stupid little errors caused by typos or not having decent intellisense is troubling. Compared to the level of tooling and safety I'm used to on the back-end, it feels like banging rocks together. Especially when we've got a gulp build process that takes long enough to run that I want to start some XKCD chair-jousting matches between edits.

wiredearp 10y ago
I am sure that the clientside developers in your company will come to realize their mistake when they see your interfaces and level of tooling.
- douche 10y ago
  The willfull resistance to embrace practices that make development easier, more efficient, and safer is baffling.
  - shados 10y ago
    then just get the logical conclusion and use ReasonML/Elm/PureScript/whatever for the frontend instead. Oh, you meant easier/more efficient/safer but only within the comfort zone...makes sense.
    - douche 10y ago
      Baby steps, baby steps. It's a process.
bloopalert 10y ago
Your gulp job sounds like the real issue. Use IntelliJ and that fixes a lot of the problems
- pluma 10y ago
  Or Webpack. Or stop running every dependency through Babel (which is the biggest source of build slowness I've seen in the wild).