continue trying to learn haskell through doing advent of code!
I’ve been doing this too! It’s been strange, mainly since I’m not used to Haskell’s approach to problems. I have some familiarity with thinking about things functionally, but not as much as Haskell requires. I guess that’s what practice is for!
I got the job I interviewed for last week (contingent on a reference check), and I start January 4th. So I’m hoping this light “covid fatigue” and lingering cough go away so I can enjoy my last 3 weeks off.
This week I’d like to get in a couple days of skiing and a few mountain bike rides.
At the moment waiting for the official offer on a job that, at least to start, would be part time doing odd jobs for a startup trying to make more rigorous software testing a thing. As I understand it, small standalone projects, helping write more technical blog posts, telling them their docs make no sense to anyone who hasn’t had their head deep in their product since 3 (mini) pivots ago, that kind of thing…
Also coming to terms with the apparent fact that I have much higher standards for myself than others do after what I though was an interview where I thought I really sucked it up, but they were “really excited” for me after.
Edit: Also probably putting in some more time on an ESP32 based fan controller design I want for controlling the fans in my server rack. I’ve been wanting to actually do some electronics stuff for awhile and this seems like an easy re-introduction and meshes well with trying to figure out rust on ESP chips and cleaning up my rack (And it desperately needs some dust filtering.)
Taking it a bit easy. Hopefully. I’d like to catch up on the “wouldn’t it be nice if…” backlog and sneak a few more Rust diagnostic tools into our production codebase, get people using them.
Hopefully also working more on taking my typechecker proof-of-concept to a less proof-of-concept form. This experience has given me very mixed feelings about CS papers. On the one hand, my code became 10,000% clearer once I replaced the variables a and a' and â and â' with ones like paramtype and returntype, which was a little rage-inducing. On the other hand, turns out if you can make a type checker work on simply typed lambda calculus, then it really isn’t too much harder to add a lot of more practical types to it.
$DAILYGRIND: Two pending contract offers (exploit-dev, mobile forensics), another possible pending technical screening (hw reversing).
$HOUSEKEEPING: Months without any accidents, time to redo the floors in the kitchen after the ‘puppy year’ liquid damage.
$THERAPY: Going through old notebooks and papers writing a wishlist of things I want in a CLI/TUI shell that isn’t weighed down terminal emulation, likely implementing some of it.
Current:
drag-and-drop/copy-paste prompting for saving into cwd or piping into job
all job execution being asynchronous
job output cropped and contained (expandable) into n rows with status indicator
reset/repeat any completed or current job
redirect any pending or completed job to a new window or file after the fact
assign job completion / termination to emit notification
At work: trying to continue unwinding the process my team took on before they had a manager onboard, and to shift what’s left to something that makes more sense.
For fun: catching up on Advent of Code will take up some time, but the big thing I want to do is to wrap up and release my Deno “rewrite” of jrnl (with “rewrite” in scare quotes because there are some massive differences in daily operation that came about over the past couple years as I’ve tailored things to my use cases and workflows). It’ll be the first real open-source project I’ve sincerely “published”, rather than just slapping up on my GitHub and forgetting about, which means I’ll need to make actual READMEs, add an FAQ on why you might choose it over jrnl, come up with a reasonable name, figure out whether it’ll go on GitHub or Sourcehut, etc.
I’m studying for my CCSP exam on Friday morning. The log4j shenanigans this weekend put a dent in my study time but I’m hoping to get lots of time in after work hours. If anyone has written it, I’d love some feedback on what to expect.
Finally getting around to revamping tiramisu, a touch screen tree editor prototype from 2017. I’m mostly excited about collapsing parts of the tree to s-expressions so it’s much more practical, but the overall graphic design is also improving.
Advent-of-Coding in Lean. It’s extremely slow going because it’s a Haskellish language and I’ve never Haskelled. Solved the first puzzle just last night.
Flying home from Lanzarote, going into hiding until my arrival test results come back then heading to Wales to help deliver my friend’s boat to the port it’s wintering in. Going from 24°C and sunshine to 4°C and wet in 36 hours is going to be quite the shock.
Rest of week is getting back into the swing of things at home, everyone out of isolation and back to normal. Still have things in the homelab to tidy up and experiment with, my long running battle with the “media server” apps getting wedged occasionally and having to respond to a family P1 (which are really P3s, admittedly) is ongoing currently.
Hopefully implementing job control and also working on some finishing touches for the customizable prompt for crust
Working on some side projects like a file manager and a project that exports currently installed Rust crates and allows you to manage them (via install/uninstall/etc)
Finals week! Which is busy for my students but mostly waiting around and answering the occasional question for me (they are working on final projects). As a result, picking back up a research project that had mostly gotten shelved during the semester.
Navigating the hilariously bad information about pre-flight COVID testing to make sure that when the family gets to the Big Island of Hawai’i we don’t have to quarantine. Hopefully, this will lead to an actual series of flights to the Big Island, where we’re staying for a month with family.
Otherwise, catching up on Advent of Code, and working(ish).
Probably gonna be enjoying the last bit of above freezing weather of the year and playing with JavaScript custom elements to try and experiment with making the little conversation snippets in my blogposts easier to write. Right now I have everything put into a markdown link like this:
[These are some words that have been said. Have <a href="https://google.com">a link</a>.](conversation://Mara/hacker)
But if I convert this to a custom element, it could look like this:
<xeblog-conversation character="Mara" mood="hacker">
These are some words that have been said. Have [a link](https://google.com).
</xeblog-conversation>
The main downside of this is that I’d start to have structural JavaScript in my blog again (a few rewrites ago it was totally rendered on the client with PureScript and React), which means that I’d be slightly going back on one of the design goals of my blog in its current form. However, I think that it would be good because I’d be able to use vanilla Markdown again instead of my current super hacky link postprocessor. This may also make people reading the RSS feed get a bad experience, however they have one already.
If anyone has any thoughts on this, I’d be welcome to hear them.
Interviewing. There’s a startup I’m actually really excited about but their process is looooong. Other than that breaking back into an old project I haven’t looked at in like a year.
Maaaybe getting a blog going finally. I’ve been noticing alot of simple concepts that don’t have simple resources explaining them. You have to assume some prior knowledge, but most resources don’t attempt to minimize it. Wavelet Trees for example are very simple and useful, but articles always reference some other structure or use academic terms that exist only as a form of indirection. So maybe I’ll take a crack at that.
At work, paying down some technical debt, and then hopefully making progress on an AI/ML project.
Updating my LinkedIn and seeing what opportunities are out there.
Rust meetup on Thursday at the Austin Public Library.
Dawn lang: hopefully making some progress on formalizing the untyped multistack concatenative calculus.
Continuing to work on developing solid relative pitch using the “Complete Ear Training” Android app. Piano lesson on Tuesday.
And if I have some free time, either continuing AoC (in Rust) and/or continuing working on the browser-based implementation of Quoridor that I started over the weekend.
Writing job descriptions for the next couple developers we’ll be hiring onto my team. It’s a small company and right now I’m the only full-time backend person.
Having to do this isn’t ideal for me. My manager is totally swamped and delegated a bunch of recruiting-related stuff to me and one of my teammates: writing job descriptions, screening resumes, doing initial screening calls, and working with the recruiters. Exactly the sort of stuff that caused me to realize I was far, far happier as a developer than a manager when I tried going into management years ago. I recognize that it was the right call to delegate some of it to me, but that doesn’t mean I’m going to enjoy it. Oh well, that’s why it’s called “work” instead of “play.”
Putting in my notice at my current job, then presumably working on all the ‘urgent’ things my boss was expecting me to do but hadn’t told me about….
outside of work going to continue trying to learn haskell through doing advent of code!
Congrats! If you can afford it, I hope you’re able to take some time off before the next gig.
Congratulations! Break a leg.
I’ve been doing this too! It’s been strange, mainly since I’m not used to Haskell’s approach to problems. I have some familiarity with thinking about things functionally, but not as much as Haskell requires. I guess that’s what practice is for!
Maybe these threads instead can become “what did you do last week”? I never wanna jinx future plans ♥
I got the job I interviewed for last week (contingent on a reference check), and I start January 4th. So I’m hoping this light “covid fatigue” and lingering cough go away so I can enjoy my last 3 weeks off.
This week I’d like to get in a couple days of skiing and a few mountain bike rides.
I’m also reading “Topology and its Applications” and trying to work through some of the problems.
Finally, I’m doing code cleanup and documenting the OpenGL library I’ve been working on.
Congratulations!
Thank you!
At the moment waiting for the official offer on a job that, at least to start, would be part time doing odd jobs for a startup trying to make more rigorous software testing a thing. As I understand it, small standalone projects, helping write more technical blog posts, telling them their docs make no sense to anyone who hasn’t had their head deep in their product since 3 (mini) pivots ago, that kind of thing…
Also coming to terms with the apparent fact that I have much higher standards for myself than others do after what I though was an interview where I thought I really sucked it up, but they were “really excited” for me after.
Edit: Also probably putting in some more time on an ESP32 based fan controller design I want for controlling the fans in my server rack. I’ve been wanting to actually do some electronics stuff for awhile and this seems like an easy re-introduction and meshes well with trying to figure out rust on ESP chips and cleaning up my rack (And it desperately needs some dust filtering.)
Patching things because of a log4j CVE…..
Taking it a bit easy. Hopefully. I’d like to catch up on the “wouldn’t it be nice if…” backlog and sneak a few more Rust diagnostic tools into our production codebase, get people using them.
Hopefully also working more on taking my typechecker proof-of-concept to a less proof-of-concept form. This experience has given me very mixed feelings about CS papers. On the one hand, my code became 10,000% clearer once I replaced the variables
aanda'andâandâ'with ones likeparamtypeandreturntype, which was a little rage-inducing. On the other hand, turns out if you can make a type checker work on simply typed lambda calculus, then it really isn’t too much harder to add a lot of more practical types to it.$DAILYGRIND: Two pending contract offers (exploit-dev, mobile forensics), another possible pending technical screening (hw reversing).
$HOUSEKEEPING: Months without any accidents, time to redo the floors in the kitchen after the ‘puppy year’ liquid damage.
$THERAPY: Going through old notebooks and papers writing a wishlist of things I want in a CLI/TUI shell that isn’t weighed down terminal emulation, likely implementing some of it.
Current:
At work: trying to continue unwinding the process my team took on before they had a manager onboard, and to shift what’s left to something that makes more sense.
For fun: catching up on Advent of Code will take up some time, but the big thing I want to do is to wrap up and release my Deno “rewrite” of jrnl (with “rewrite” in scare quotes because there are some massive differences in daily operation that came about over the past couple years as I’ve tailored things to my use cases and workflows). It’ll be the first real open-source project I’ve sincerely “published”, rather than just slapping up on my GitHub and forgetting about, which means I’ll need to make actual READMEs, add an FAQ on why you might choose it over jrnl, come up with a reasonable name, figure out whether it’ll go on GitHub or Sourcehut, etc.
Looks like it’ll be bug finding and fixing all week long.
I’m studying for my CCSP exam on Friday morning. The log4j shenanigans this weekend put a dent in my study time but I’m hoping to get lots of time in after work hours. If anyone has written it, I’d love some feedback on what to expect.
Finally getting around to revamping tiramisu, a touch screen tree editor prototype from 2017. I’m mostly excited about collapsing parts of the tree to s-expressions so it’s much more practical, but the overall graphic design is also improving.
This could make it possible to write clojure without my computer! At least capture it. Very exciting.
Advent-of-Coding in Lean. It’s extremely slow going because it’s a Haskellish language and I’ve never Haskelled. Solved the first puzzle just last night.
Flying home from Lanzarote, going into hiding until my arrival test results come back then heading to Wales to help deliver my friend’s boat to the port it’s wintering in. Going from 24°C and sunshine to 4°C and wet in 36 hours is going to be quite the shock.
Rest of week is getting back into the swing of things at home, everyone out of isolation and back to normal. Still have things in the homelab to tidy up and experiment with, my long running battle with the “media server” apps getting wedged occasionally and having to respond to a family P1 (which are really P3s, admittedly) is ongoing currently.
Finals week! Which is busy for my students but mostly waiting around and answering the occasional question for me (they are working on final projects). As a result, picking back up a research project that had mostly gotten shelved during the semester.
Navigating the hilariously bad information about pre-flight COVID testing to make sure that when the family gets to the Big Island of Hawai’i we don’t have to quarantine. Hopefully, this will lead to an actual series of flights to the Big Island, where we’re staying for a month with family.
Otherwise, catching up on Advent of Code, and working(ish).
I’m setting up my homelab with new ASUS PN51 Mini PC Barebone with AMD Ryzen 3 5300U general purpose nodes!
Probably gonna be enjoying the last bit of above freezing weather of the year and playing with JavaScript custom elements to try and experiment with making the little conversation snippets in my blogposts easier to write. Right now I have everything put into a markdown link like this:
But if I convert this to a custom element, it could look like this:
The main downside of this is that I’d start to have structural JavaScript in my blog again (a few rewrites ago it was totally rendered on the client with PureScript and React), which means that I’d be slightly going back on one of the design goals of my blog in its current form. However, I think that it would be good because I’d be able to use vanilla Markdown again instead of my current super hacky link postprocessor. This may also make people reading the RSS feed get a bad experience, however they have one already.
If anyone has any thoughts on this, I’d be welcome to hear them.
I mean, Markdown can include HTML elements in many implementations, and you could expand things in the RSS feed, if you’re feeling up to that?
Granted, I’m not one to write a static site generator in Rust, but that’s down to me wanting to keep things scripty on my side projects.
[Comment removed by author]
Interviewing. There’s a startup I’m actually really excited about but their process is looooong. Other than that breaking back into an old project I haven’t looked at in like a year.
Maaaybe getting a blog going finally. I’ve been noticing alot of simple concepts that don’t have simple resources explaining them. You have to assume some prior knowledge, but most resources don’t attempt to minimize it. Wavelet Trees for example are very simple and useful, but articles always reference some other structure or use academic terms that exist only as a form of indirection. So maybe I’ll take a crack at that.
Writing job descriptions for the next couple developers we’ll be hiring onto my team. It’s a small company and right now I’m the only full-time backend person.
Having to do this isn’t ideal for me. My manager is totally swamped and delegated a bunch of recruiting-related stuff to me and one of my teammates: writing job descriptions, screening resumes, doing initial screening calls, and working with the recruiters. Exactly the sort of stuff that caused me to realize I was far, far happier as a developer than a manager when I tried going into management years ago. I recognize that it was the right call to delegate some of it to me, but that doesn’t mean I’m going to enjoy it. Oh well, that’s why it’s called “work” instead of “play.”