Perl was my first real language, too, but I haven't used it in years. Others complain about the sigils and referencing rules but I learned them early, when I was young, so I guess I didn't know any better.
I even had a job where we created a featureful website with just perl, DBI, and no framework except a simple module written by a programmer who left the company before I was hired. I look back to that job fondly, because everything seemed much simpler. Only bad thing about it was the paycheck. :)
How do you use org-mode to automate pull-requests? Do you make the pull request inside emacs? Are you using it to compile a note from all of the commits in a certain branch? Or something else?
Preface: I like very detailed pull-requests. For me this includes JIRA information and implementation notes. Most of my recent work has been backend API stuff, and org-babel/restclient [0] lets me do fast test-driven-development in the same file. These inputs / outputs are included in the PR render so it's easy to see what the API is doing.
> How do you use org-mode to automate pull-requests?
I have a script called 'new_jira $JIRA_NUMBER' which pulls relevant JIRA information from the REST API and generates an org-mode file. I do my work and list implementation details, gotchas, and generally narrate work done. Details are light for easy tickets, and heavy on complex ones. Finally, render it as markdown and copy/paste in the GitHub PR field.
I also include tips / tricks if it's not appropriate to comment directly in the code base. I come back and search for these later (knowledge base).
> Do you make the pull request inside emacs?
I've usually faced admin issues trying to get the necessary tokens to make PRs in emacs. Just render, copy & paste in the PR title/description field.
> Are you using it to compile a note from all of the commits in a certain branch?
That's right. All work relevant to a particular ticket is captured in a single org-mode file. I keep my git history clean and well documented so it's not necessary to use these files to understand commit history though.
> Or something else?
For work unrelated to the JIRA flow (e.g. security bug hunting) I use org-mode to track the entire narrative and use org-babel to inline code necessary for the exploit. This makes security reporting easy as I just render as PDF and shoot it off to the security people.
I've spent some time learning it that I don't regret.
However, I dislike the GenServer syntax, it feels too complicated with random tuples all over the place. Also, I feel like the job market is too small. I wasn't able to find a job using it (although maybe COVID is to blame here).
The job market for Elixir is pretty small. Sure, there are a couple of people here responding with specific listings, but still. I was hoping it would have ramped up by now but it seems that it's going to stay a niche player.
This is how I feel too, and I'm a confused how the reaction to hooks is so overwhelmingly positive. I find it quite strange that we need to set up an eslint rule to make sure our function arguments are correct, and it will automatically fill them out if we don't. And I need to memoize so many things! I feel like I'm not even writing javascript anymore.
I have 10 years experience, no degree, and yeah, submitting my resume online seems like throwing it into a black hole. And I have always been one of the top performers at my previous jobs. I did get about 20-25% interviews though, so I guess I just need to apply to a large number of jobs and I'll eventually get through.
I even had a job where we created a featureful website with just perl, DBI, and no framework except a simple module written by a programmer who left the company before I was hired. I look back to that job fondly, because everything seemed much simpler. Only bad thing about it was the paycheck. :)