Skip to main content


I am in urgent job search mode, so I'm gonna throw this out here and see if anything comes of it.

I am a #Canadian, fluent in both #English and #French. I have experience with several programming languages. My strongest proficiency is with #Haskell and #C. I also have a reasonable grasp of #HTML, #JavaScript, #SQL, #Python, #Lua, #Linux system administration, #bash scripting, #Perl, #AWK, some #Lisp (common, scheme, and emacs), and probably several others I've forgotten to mention.

I am not necessarily looking for something in tech. I just need something stable. I have done everything from software development, to customer support, to factory work, though my current circumstances make in-person work more difficult than remote work. I have been regarded as a hard worker in every job I have ever held.

#GetFediHired

in reply to LoranJohn

@LoranJohn I honestly haven't touched LinkedIn in years. I never used of seriously. I'm going to have to reactivate it. My first priority was getting my resume updated.

Edit: I've gotten into it, but it's in serious need of updating.
linkedin.com/in/jonathan-lamot…

in reply to Jonathan Lamothe

I resume` shell is useful but I find cover letters more compelling. A simple one page missive showing you have researched the company you're applying to and have an understanding of why they may want to be hiring you shows initiative. Dress comfy, address the interviewers as equals to the point of inquiring as to their day and express annoyance if they stray out of bounds - you don't want to work for assholes.
in reply to Jonathan Lamothe

have a try here ? careers.ovhcloud.com/ and search for Beauharnois. HTH


So, I've been taking another run at learning #CommonLisp. The last time I tried, I simply could not wrap my brain around macros. I'm reading the same book again, but this time am a more experienced programmer, and it all just clicked in my head.

I might actually end up enjoying #Lisp after all. I don't know if it'll dethrone #Haskell, but I'm starting to get why people like it.

reshared this

in reply to Jonathan Lamothe

Don't start with macros. It doesn't make sense to until you really get the "vibes" of how it all goes together.

I've seen so much common lisp code out there that doesn't ever touch macros. They are super powerful, but you don't need them until you do.

Having Haskell down though, you are probably most of the way there.

in reply to Karsten Johansson

@Karsten Johansson Tell that to the author of Practical Common Lisp.

That said, I get it now. It's so stupidly simple when it finally makes sense.

Also, yeah, learning Haskell in the interim helped a lot.

in reply to Jonathan Lamothe

I like the book enough that I bought a physical copy of it.

Siebel (the author) said, back when Twitter was Twitter and everyone liked it just fine, that he was considering updating and adding a few chapters. afaik he hasn't, but it brought my hopes up quite a bit. :ablobcatrave:

If you want truly complicated, check out the book Let Over Lambda. It is mind blowing, but you'll come away from it with a whole new level of understanding.

in reply to Karsten Johansson

@ksaj
one can get pretty far without macros, but there are certainly some scenarios where macros are needed and super helpful.

The main use case is to control the evaluation (order, timing) of arguments. Can't do it with functions.

@me

in reply to hajovonta

@hajovonta Sure, but that isn't what was being said. The point was only that one doesn't need to think Lisp is too complicated just because of macros. They are not the right place to start. Hence the bit about not starting with them.


Does #Haskell's microlens-platform really not have a function of type Int -> Lens' [a] a?

That seems an odd omission.



!Haskell Users Group (unofficial)
Has anyone successfully cross-compiled a #Haskell project to .exe from a *NIX system (preferably Debian)? I've casually looked into it in the past, but never given it a serious try.


I hate it when I make an official release of a program with an ugly snippet of code that I can't figure out how to write more cleanly, only to come up with a solution 10 minutes after pushing the release. I just make the change in the dev branch so it gets incorporated into the next version.

In my defense, the thing I was overlooking was that #Haskell's Maybe type is an instance of Foldable. It's not the kind of data type that exactly screams Foldable, is it?

Side note: I should use Hoogle's search by type signature feature more frequently. I needed a function that looked like this: Monad m => (a -> m ()) -> Maybe a -> m (), which is literally just mapM_.

in reply to Jonathan Lamothe

I don't use emacs, but it works well in Neovim and VS Codium. I've heard it's better in emacs than in vim, but haven't verified that.


!Haskell Users Group (unofficial)
So, I created a #Haskell #TUI program using brick. I wanted to have it support cursor keys, as well as vim and Emacs-style cursor movement, but for whatever reason I can't get it to register C-n and C-p keypresses. C-f and C-b worked fine though.

Anyone have any ideas as to why this might be?

The repository is at: git.fingerprintsoftware.ca/jla…

reshared this



TIL:
data Foo = Bar { val :: Int } | Baz { val :: Int }

is valid #Haskell. I wouldn't have thought you could define val twice like that.


GHCup: Because #Haskell apparently needs a package manager for its various package management systems.


I'm an idiot.

I was trying to install #Haskell on a machine and thought the installer was taking a really long time. In my defense, the last line of text was:

Installation may take a while.

It sat at this stage for over an hour while I did other stuff, because I hadn't bothered to read the previous line:
Press ENTER to proceed or ctrl-c to abort.
in reply to Jonathan Lamothe

It's not you, it's bad design. The prompt should always be the final line of output.


I wonder how many times I'm going to have to re-learn how to use lenses in #Haskell.


Did #Haskell at some point make defining a module without an explicit list of names to be exported illegal? It's yelling at me when I try to do this now.
in reply to Jonathan Lamothe

I noticed a while ago that they added a warning for that but it would still compile, but I wouldn't be completely surprised if it were an error now.
It's actually annoying in ghci because the warning gets repeated every time you define something.
in reply to Jeremy List

@Jeremy List No, it's still just a warning. I was using the --pedantic flag though (which turns warnings into errors).


Okay, I'll admit it. Using #Haskell to talk to an #SQL database is not my favourite thing.
in reply to Boyd Stephen Smith Jr.

@Boyd Stephen Smith Jr. It's not so much the SQL part that's the irritating bit. It's that it doesn't really mesh super well with "the Haskell way of doing things".
in reply to Jonathan Lamothe

@BoydStephenSmithJr understandable. There's always a tension between "pleasant for the Haskeller" and "pleasant for the DBA" (or general SQL knower). We have the same problem at work (we sacrificed our DBA and used flora.pm/packages/@hackage/hpq… and its eDSL)

This website uses cookies. If you continue browsing this website, you agree to the usage of cookies.