Honestly designing a parser is easy: just start using ANTLR and perhaps add later an AST layer. However if you do not want to go that I suggest looking in projectional editing, for example JetBrains MPS or Freon by Jos Warmer
Consider also that many companies promote job ads on LinkedIN or search candidates on LinkedIN. So even without the “submit your application” LinkedIN is pretty important to get hired, imho
Strumenta | Project Manager with Marketing skills | Italy (Remote) | Full time
We are a small company (6 persons) but we are punching above our weight. We have a significant worldwide reputation in our niche and we work with clients distributed across the USA, Europe, and Asia.
While we are registered in Italy, we very rarely have Italian clients. Our working language is English and we would need an English native speaker or someone very fluent in English. If you are not an English speaker, you have not lived for at least one year in an English speaking country, and you have not used English as a working language in the past, please do not apply.
Your role would be ensuring that the most critical things get done, using your judgment to ensure they get done efficiently and effectively. You would be essential in solidifying our good practices, improving them, and identifying how we can improve.
You will guide us specifically on delivery and marketing.
On delivery, you will be in charge of communication and coordination with clients, supervise how projects progress, and measure profitability.
Regarding marketing, you will manage the different activities to ensure we communicate what we are doing clearly and to the right target.
Personally I work in the Language Engineering area and it seems obvious that you want tax lawyers and accountants to interpret the tax code and translate it into “code”. Is just that you also want “code” to be obvious for them and support by proper tooling, which catch all inconsistencies.
I would also love to interview the author of this and the work for mon-entreprise. While I understand French, I also have these interviews in English to reach more people
..wow, this is a bit strong. I would encourage you to be more respectful of persons who work in this very specific field and share their ideas. There are always persons behind some work you insult so easily.
You know, there are over 2M persons who read our articles. A few hundred also bought a book or a video-course from us, but the vast majority just got some information from free, and we like it in this way. I do not think we got so many persons interested in what we do by lying.
If you have a different professional experience I would happy to learn from it.
"Seibel: And are there development tools that just make you happy to program?
Thompson: I love yacc. I just love yacc. It just does exactly what you want done. Its complement, lex, is horrible. It does nothing you want done.
Seibel: Do you use it anyway or do you write your lexers by hand?
Thompson: I write my lexers by hand. Much easier."
I happen to like both bison and flex, which are relatively easy to use and bug-free in my experience. Yet your article spreads hundreds of lines of FUD about these tools, a strategy that many ANTLR people use.
I have used ANTLR. It is not intuitive, the documentation is horrible, if you happen to find some advice on Stackoverflow it is likely to be for another one of the incompatible versions.
I suppose if you use ANTLR long enough, these problems go away. But bison or Menhir don't have these problems in the first place.
I think that hand-rolled parsers are good if:
1) You have a team that knows well what they are doing
2) You have a lot of resources
3) Your language is stable
I would argue that parser-generators are what made those projects to be started and prosper in the first place. Then once one is successful a custom solution could make sense but in my experience it is more expensive and potentially less maintanable, unless you know very welll your way around parsers and language tooling
So I will rest for a few days :D