But for something even more fun, I suggest you check out Marpa (https://jeffreykegler.github.io/Marpa-web-site/). It is, by far, the nicest parsing tool I have ever worked with. Being able to parse ANY BNF is huge. And the state tables for debugging! Knowing what possibilities you have makes things way easier. Especially for getting stuck in an ambiguous spot of your grammer. Finally, using ruby slippers to get out of a tight spot is hugely useful.
My one complaint is that the only implementation is in Perl. The core engine is written in C though, so someday I would like to convert the Perl into Python. I started several months ago, and haven't been able to get back to it. (https://github.com/srathbun/pyMarpa)
I would guess you aren't thinking in the language in question. You are translating your native language sentence into the appropriate english sentence on the fly. To use a programming analogy, it is like writing Haskell code as if it was C. Because you aren't thinking functionally, for every imperative step the C code in your head takes you have to translate it to some sort of functional analog.
You can get through it, but it is slower, and looks "funny" to a "native".
Python-mode provides awesome sause :) To get the repo, clone it recursively, or you won't have all the submodules. `git clone --recursive https://github.com/srathbun/vim-plugins.git ~/.vim`
This is one thing I don't understand about people working in startups. You are in the business of you. The startup is in the business of the startup. Don't conflate the two.
That's the way I looked at it. Get through it without a lot of debt and be a big fish in a little pond.
I'm smart enough to work on "hard" problems, but the stuff I do now is interesting, and while my gross income is lower, my net income is quite a bit higher.
But for something even more fun, I suggest you check out Marpa (https://jeffreykegler.github.io/Marpa-web-site/). It is, by far, the nicest parsing tool I have ever worked with. Being able to parse ANY BNF is huge. And the state tables for debugging! Knowing what possibilities you have makes things way easier. Especially for getting stuck in an ambiguous spot of your grammer. Finally, using ruby slippers to get out of a tight spot is hugely useful.
My one complaint is that the only implementation is in Perl. The core engine is written in C though, so someday I would like to convert the Perl into Python. I started several months ago, and haven't been able to get back to it. (https://github.com/srathbun/pyMarpa)