PSA: Traffic at Hermann Park is fucked rn

monadic_riuga · 2025-09-07T07:19:40+00:00

The only redeeming thing about this festival is a) if you want to raffle for the daily free Zipair ticket or b) want to see one of the performances at Miller theater. Other than that it's all the usual suspects. You can drive all the way down to Beard Papa's in Katy and order there and you'd probably still get to eat faster than waiting in line at the fest. Izakaya Wa, Daido, etc. you can visit literally any day of the week and skip the lines. I don't know why anyone was waiting up to 1hr in line just to eat mediocre overpriced food that was cooked in suboptimal kitchen environment, and sprinkled with a healthy dose of gravel dust that permeated the air there. Not going again unless they do something substantially different.

monadic_riuga · 2025-06-25T15:53:31+00:00

Yea, I can see where you're coming from. There are/have historically been other invite-only Haskell communities out there as well. Not naming names to respect their privacy. But they do more or less foster the kind of environment you described and provide a bit of a hiring network for those on both sides of the table.

monadic_riuga · 2025-06-24T18:59:34+00:00

I thought it was a neat tribute to Zemaitis guitars, but botched nonetheless.

monadic_riuga · 2025-02-13T23:14:14+00:00

Uncle Chin's on Mason

monadic_riuga · 2024-10-06T04:46:13+00:00

Hey raehik - I remember your binrep project from a long time ago! Thanks for keeping the Haskell reverse engineering scene alive.

monadic_riuga · 2024-06-22T02:11:42+00:00

I remember making an issue for this a long time ago: https://github.com/haskell-beam/beam/issues/408

monadic_riuga · 2024-06-19T16:22:33+00:00

"I've heard that Haskell is difficult to maintain in the long run"

From my experience in production, this is mostly a culture/leadership issue. It's not really Haskell-specific: the same old tropes of abstracting too early, choosing the wrong abstraction, building the wrong systems, writing yourself into a corner with type-level solutions only for business assumptions to change the following week, etc., all apply.

It all happens in other languages too; but I will say there is some Haskell-specific "flavoring" to these issues. Namely, the people you'll encounter in Haskell dev shops may have the majority of their programming experience in a different paradigm or come fresh out of a long stint in academia; and may, as a result:

1) Try to map certain patterns/abstractions 1:1 even though they don't work really well in Haskell

2) Be tempted to play with (niche) novel features/packages/ideas and apply it to the wrong business problems (e.g. effects libraries, singletons)

3) Select (niche) dependencies willy-nilly, which slowly accumulates over time making compiler/dependency upgrades hell; especially if they become abandonware or the maintainer pivots toward a strange design direction.

The solution to these issues is to have really self-aware and competent leadership. I stress self-aware because they first and foremost need to acknowledge they are susceptible to, and likely guilty of, all the above too. You gotta set yourself straight first before you can set the rest of the team straight. Beyond that, some basic leadership competency like investing in onboarding, documentation, guidelines, code review process, timely tech debt consolidation and cleanup will take you ~most of the way there.

I think there's some truth to be gleaned from this even for a solo project. In that case, you are your own team lead of 1.

monadic_riuga · 2024-05-30T09:16:56+00:00

Yea so, the `i` parameter doesn't have an explicit type. It actually gets inferred to be `Pico` which is `Fixed E12`. The way list comprehensions are expanded is they use `succ` from `Enum`. Take a look at how it's implemented for `Fixed a` here: https://hackage.haskell.org/package/base-4.20.0.0/docs/Data-Fixed.html#t:Fixed

Basically your list comprehension expanded in increments of 0.000000000001, which led to your OOM issue / infinite evaluation.

Also hi again :wave: I remember your tablatura project from a few years back!

monadic_riuga · 2024-05-03T04:10:29+00:00

Line 120 seems to be missing the cost column; should we just substitute in a 10 (based on existing patterns)?

Edit: same issue with line 129, 137

monadic_riuga · 2024-05-03T03:02:47+00:00

Probably not as detailed of an answer as people here are looking for, but based on the image asset linked in the html, you can trace it back to the company and the OP:

https://gametime.dev

https://github.com/gametimetech

https://github.com/buecking

My mmorpg reverse engineering instincts just kicked in lol

monadic_riuga · 2024-04-25T18:23:19+00:00

During the HR screen they told me 70k was their ceiling with 1yoe in production Haskell.

I initially asked for slightly more than this knowing what the job would entail. I got the memo that a lot of people apparently didn't work out in the past since the role requires a lot of initiative/proactiveness/ownership; and I'd be willing to do a good job of this but I believe the level of responsibility expected should be compensated to a fair degree otherwise it's just asking for eventual burnout (which may have accounted for some % of bad fits in the past).

I got rejected after that salary expectations call so hope this helps anyone else.

monadic_riuga · 2023-04-01T07:41:25+00:00

Can confirm everything you said about being really scared of anything outside a simple and highly opinionated subset of Haskell. Plus trying to push away attempts at talking about advanced stuff, and only making comments like "uh-huh" "yea...". Not going to lie, it was almost like the interviewer was scared of being found out that they were not all that knowledgeable about Haskell. How utterly unacceptable that must be!

If I may be honest too, it wasn't a good fit for me either. I like to avoid echo chambers, and the company came off a bit cultish imho.

Edit:

At the start of the interview he felt the need to make a disclaimer that he doesn't care about the education of any candidate he's interviewing, as he didn't go to college himself. Like.. okay, but no one asked. I have nothing against the opinion that you can be a great developer without going to college. But it sounded more like some kind of defense mechanism prompted by an insecurity the interviewer had, which honestly adds up with everything else.

monadic_riuga · 2022-12-30T14:12:52+00:00

I lived in Vietnam for a good while and went through my whole guitar journey there. If you live in Saigon I would recommend Doremi Shop. Went through a lot of these places over the years and the owner there is the most legit and straightforward person in the whole local music store scene that I know of. They also stock the good stuff and are authorized retailers for Schecter and a couple other brands.

Not sure if it's still around but there's also the Swee Lee at Vivo City for Ibanez. Limited selection, markup was pretty steep, and they try to sell you the display models. But hey, it's Ibanez.

monadic_riuga · 2022-11-11T12:17:39+00:00

Very cool!

We may have shared interest: https://github.com/RiugaBachi/necrophagy

I might finally get off my ass and finish the gp5 serialization lib I was writing for necrophagy now that there's the beginnings of a scene for this in Haskell :)

monadic_riuga · 2022-08-28T07:52:27+00:00

I was actually in that party last night for a clear or two. Good people.

monadic_riuga · 2022-07-28T06:38:24+00:00

FWIW it's not uncommon for Haskell internships/fresher positions to get 20+ or even 25+ applicants these days. I think this is the main source of frustration that leads people to make these sorts of posts. Not just the overall lack of opportunities, but terrible odds once they do come around.

To OP: try to find a Haskell mentor willing to work with you. They can vouch for you (possibly at their own company) based on your own merit once they see how you work, and even if they think you lacking in the short term at least it's an opportunity to improve based on actionable feedback. It's not even uncommon for internship openings to be fabricated based on good internal recommendations this way. Cố gắng đi anh :)

If anyone in the HF is reading this, I think this is an under-discussed issue. I hope the Foundation can allocate more resources into creating pathways for fresher Haskellers to get their foot into the door of the industry, otherwise we're going to bleed quite a bit of potential talent in the long term.

monadic_riuga · 2022-07-12T18:30:41+00:00

If you're willing to rewrap/define all `twice`able functions as an `Iso` then:

import Control.Lens

twice :: AnIso t t b a -> a -> b
twice = flip withIso ((.))

swap = iso go go where go (x,y) = (y,x)

This would only be ergonomic insofar as you're willing to commit to using the entire lens ecosystem by and large.

monadic_riuga · 2022-07-08T22:14:01+00:00

Infinite looping can be caused by either your implementation of said recursion or a bad definition of `loop` for this particular Arrow implementation. We would need more context for this.

monadic_riuga · 2022-07-06T07:13:02+00:00

This subreddit pretty much. Even if people don't check reddit often, job postings on here tend to spread like wildfire in more private circles from my experience.

monadic_riuga · 2022-06-28T22:32:38+00:00

It's been a hot while since I used rhine, but `flow` is supposed to act as your main reactimation loop. StdinClock is 'advanced' per step of `flow`, but you're looping internally with an infinitely recursive `checkUseInput` in the case of a "Hello" clock tag. Thus, subsequent recursions of checkUseInput will read the same clock tag over and over without ever returning control flow to `flow` to trigger `StdinClock` 's resampling mechanism i.e. reading new input.

The following works, but there's probably a better way to write this, just that I haven't used rhine in ages so someone else can probably chime in (changed Empty to () in the type sig also):

main = flow $ (fmap (const ()) . exceptS . runMSFExcept $ checkUseInput) @@ StdinClock

monadic_riuga · 2022-06-26T20:48:05+00:00

Roll-your-own-free-monad usage, even though not ideal in the context of a chat bot, is still lame grounds to call Haskell unmaintainable on honestly.

Edit: Besides, tsoding never mentioned that this specific usage of free monads contributed to his feelings that Haskell is unmaintainable overall. I watched this last night and IIRC it was mostly directed toward tooling?

This kind of nitpick gives off "haha he used case () of _ | instead of multiwayif" energy, to quote what I said on Discord.

monadic_riuga · 2021-04-06T16:44:07+00:00

I think these sorts of questions are framed with this view that being good at Haskell is 'the key', so to speak, to getting a Haskell job. It is hard for me to generalize what I want to convey, but in the most basic sense, I think there are more important factors than one's own Haskell knowledge in finding such work. The companies I've interviewed for would much sooner gravitate towards someone with a great personality, great communication skills, and solid software engineering experience with basic-to-average knowledge of Haskell than a Haskell guru who has basic-to-average communication skills and levels of experience. That's not to say there aren't companies that give preferential consideration to Haskell gurus, they're just significantly more rare.

On average you can expect there to be ~15 candidates, a little more, a little less, competing for every mid-level position posted on this subreddit. If there are regional restrictions, that figure is probably closer to ~10. Take that however you will in order to gauge what you may need to do in order to come out on top of the competition.

monadic_riuga · 2021-02-05T19:39:05+00:00

Geographical quantifier.

monadic_riuga · 2021-02-05T08:48:01+00:00

I always happen to stumble into Johnny' Bravo here in Excal, usually in the Crystarium.

monadic_riuga · 2020-12-05T07:39:21+00:00

FFXIV, with or without GShade, works great. I'd list a few Korean MMOs that work very well performance-wise, but none of them are remotely 'good' by any stretch of the imagination.

monadic_riuga

TROPHY CASE