Brian Jones

@mojobojo

Software Architect & Software Engineering Manager @ AlasConnect -

Anchorage, Alaska
Vrijeme pridruživanja: travanj 2008.

Tweetovi

Blokirali ste korisnika/cu @mojobojo

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @mojobojo

  1. 1. velj

    5. That all said, if I hadn’t just moved to and bought a house up here in Alaska... I want my team to be satisfied and productive, but also want to do what I enjoy as well (mentoring and building and learning more in ).

    Prikaži ovu nit
    Poništi
  2. 1. velj

    4. We won’t necessarily drop completely. We still think it serves as the proper tool for where we want bullet proof type safety on more complex systems. We have to support everything we have built anyways, and it still worth teaching people FP concepts.

    Prikaži ovu nit
    Poništi
  3. 1. velj

    3. While I think the guys behind Reflex have done an amazing job, the nix ecosystem around it is yet another complex poorly documented system with which new devs need to learn. While I would prefer purescript here, it sounds like the team wants to explore elm.

    Prikaži ovu nit
    Poništi
  4. 1. velj

    2. My primary senior dev has suggested we use Go (something I had previously used at this company), since a lot of the work is likely bog standard web APIs. The language is, frankly, boring, but I suppose in a good way. A dev can be productive in an hour.

    Prikaži ovu nit
    Poništi
  5. 1. velj

    To answer a few moving away from questions: 1. Our company is scaling out fast, and part of that is dev professional services. Perhaps in this case bringing new hires up to speed in the average 3 months isn’t reasonable given how fast the Cs want to take on customers.

    Prikaži ovu nit
    Poništi
  6. 31. sij

    We will still use it in a limited capacity (for the beefy "no really, this needs to be type safe" problems), just not for All Of The Things as we have been.

    Prikaži ovu nit
    Poništi
  7. 31. sij

    At the end of the day (3 years) I wasn't able to take a group of non-Haskellers and get them motivated enough to stick with it long term.

    Prikaži ovu nit
    Poništi
  8. 31. sij

    Sorry community, I feel like I have failed you. My team will be discussing which tools they want to migrate to instead over the next few weeks, minus my highly opinionated position on it all 😢

    Prikaži ovu nit
    Poništi
  9. proslijedio/la je Tweet
    23. sij

    I always do year end retrospective about , but decided to do a forward looking piece instead. Haskell Problems For a New Decade

    Poništi
  10. 21. sij

    The thundering sound of ancient rushing towards your team and threatening to destroy everything you have all valiantly fought to build; negligence derived doom set forth by a series of poor choices made numerous years before any of you even came into the picture.

    Poništi
  11. 1. sij

    Hmm, last decade: - Worked at Japanese Mobile game companies building software at scale - Contracted with companies remotely - Got married - Daughter was born - Learned Haskell - Built Haskell culture and a team - Moved (back) to Alaska - Bought house - Started option trading

    Poništi
  12. 29. pro 2019.

    My 5yo daughter keeps telling me how she wants to go to the moon.

    Poništi
  13. 27. pro 2019.

    And sadly, it ties back to the original point: Documentation. I have no clue how to fix this really. I had thought I'd be writing a lot of useful blog posts these days, but I really don't have much to add outside of adoptions and mentoring anecdotes.

    Prikaži ovu nit
    Poništi
  14. 27. pro 2019.

    I still think "show me a web tutorial so I can take off and be productive" is a terrible fallacy newcomers believe will help them, because they will run into good and proper haskellisms the moment they try to do any actual work rather quick.

    Prikaži ovu nit
    Poništi
  15. 27. pro 2019.

    It's unfortunate that stacks vs cabal (and sprinkle in nix for good measure) became the fragmented thing it did 5 years ago. I think things are better now, but it circles back to the documentation point - makes it hard to buy into the language and ecosystem.

    Prikaži ovu nit
    Poništi
  16. 27. pro 2019.

    To clarify: As a community we know this, but: Our documentation sucks, and we are terrible at explaining how to use our language to others (even though great effort has gone into trying!).

    Prikaži ovu nit
    Poništi
  17. 27. pro 2019.

    My own personal irony is that while I absolutely love and would love to see it prosper further, I feel like the ecosystem itself is the actual broken part - something that recently has me entertaining other solutions for future projects.

    Prikaži ovu nit
    Poništi
  18. 16. stu 2019.

    Diving back into art these days. Value painting study.

    Poništi
  19. 11. stu 2019.

    Playing Sky with my daughter. So enjoyable!

    Poništi
  20. 30. lis 2019.

    As I interact with other peeps on here today, I sit here and silently wish my team and I were doing things a tad more interesting than what is essentially, "Enterprise, but in Haskell."

    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·