6 ms·
> Coding is a tool to get stuff done. Sure, that’s one of its roles. Racket helps me think. Maybe I’m lucky, and work on genuinely novel problems where a malle
by ashton314 3y ago
> Coding is a tool to get stuff done.
Sure, that’s one of its roles. Racket helps me think. Maybe I’m lucky, and work on genuinely novel problems where a malleable language beats libraries.
So, sure, the Racket ecosystem leaves much to be desired, but getting stuff done is only one of programming’s roles.
- namaria 3y agoPeople who use that argument are the same ones saying 'sure, I can do it in an afternoon/by tomorrow', and leave a trail of accumulating tech debt in their wake. It's a solid career move, what can I say? You get noticed for being such a sport and result oriented, and if you've got that service attitude, you get promoted/hired out of having to maintain that mess.
- ashton314 3y agoNo. Some? Maybe. All? No. I worked at a few companies where, when I needed to model a tricky system and build out an algorithm to do a tricky job, I turned to Racket as a draft. Once I got a POC done, we’d turn around and build it For Real™. If all you’ve ever done is work as an implementer, then yeah, this flow doesn’t make much sense. But I think for people who work as problem discoverers, this is more common than not.