# Haxe as a first job programming language? **URL:** https://community.haxe.org/t/haxe-as-a-first-job-programming-language/535 **Category:** Job Postings **Created:** [March 20, 2018, 2:33am UTC](https://community.haxe.org/t/haxe-as-a-first-job-programming-language/535 "2018-03-20T02:33:56Z") **Posts on this page:** 1 **Showing post:** 6
### Author: ![back2dos](https://community.haxe.org/user_avatar/community.haxe.org/back2dos/32/30_2.png) [@back2dos](https://community.haxe.org/u/back2dos) #### Post date: [May 8, 2018, 1:40pm UTC](https://community.haxe.org/t/haxe-as-a-first-job-programming-language/535/6 "2018-05-08T13:40:15Z")
> [@kevinresol](#): > > They might use TypeScript, because all the extern definitions are out there already. But with Haxe most likely you have to DIY. This is actually an opportunity. When a project starts, TypeScript devs will take the better part of a day to even configure their build process and pick their dependencies. In that time you can `haxelib install coconut.vdom` and actually build a POC that speaks for itself. In the last agency that I convinced to use Haxe, I put together over a weekend what they had planned for the first 6 weeks (and that was pre-coconut, I might add). But to be able to got at that speed, you need a firm grip not only of haxe, but of HTML and CSS (ideally an expressive preprocessor). As you’ve said it yourself, there’s no convincing people with language features (unless they are easy to present in a truly impressive way). You can however make a strong point when actually showing the emergent effect of putting these features together: a workflow that delivers at a breath taking pace. --- _[View the full topic](https://community.haxe.org/t/haxe-as-a-first-job-programming-language/535)._