adamdecaf

Scala has had a function called ??? which fills the same role and it’s really useful.

https://scala-lang.org/api/3.3.1/scala/Predef$.html#???-0

govulncheck is the much better answer and we use it.

We also let renovate[bot] (similar to dependabot) merge non-major dep updates if tests pass. I hardly notice when deps have small updates.

https://github.com/search?q=org%3Amoov-io+is%3Apr+is%3Amerge...

Compilation target support from Go and other languages makes it really easy to provide your library to websites - which we use for demos. It's quick to compile Go code into WASM and show folks quickly what your library offers.

Plus the demo's computation happens client side so no data is sent to a server.

We can offer our full payment parsing libraries to the web as developer tools without any code changes. I don't have to care about the details of WASM because it "just works".

https://moov-io.github.io/ach/webui/

Redpanda has been a superior wire-compatible alternative to Kafka for years.

https://www.redpanda.com/compare/redpanda-vs-kafka

The roles are US only currently.

Moov | Multiple Roles | Remote (US Only)

Moov powers infinite payment use cases with full data transparency. However you decide to orchestrate the motion of money: pay by bank, pay by card, disburse to a Moov wallet or linked bank account with same-day ACH or RTP®, or spend with an issued card—we’ve got you covered.

"Moov has become an integral part of our strategy at Jack Henry. Their platform’s developer-first approach allows us to innovate quickly and stay ahead of industry demands. Moov’s world-class engineering and design team has deep experience navigating complex payment infrastructure, which helps us win because we’re able to focus on building exceptional customer experiences." – Ben Metz, CTO, Jack Henry

Our technology stack includes: Go, PostgreSQL, AlloyDB, Spanner, Kubernetes, Docker, GCP, OpenTelemetry, Kafka, and more.

Open Roles:

- Senior Software Engineer ($165k–$185k)

- Senior Software Engineer – Front End ($145k–$160k)

- Director of Risk Operations ($175k–$190k)

- Account Manager (Base $120k–$140k, Commission $60k, OTE $180k–$200k)

- Enterprise Account Executive (Base $155k–$175k, Commission $150k, OTE $305k–$325k)

Don't see your preferred role? Email careers@moov.io with your resume.

Apply: https://moov.io/careers/#open-roles

Website: https://moov.io/

There's quite the mix of languages involved!

    -------------------------------------------------------------------------------
    Language                     files          blank        comment           code
    -------------------------------------------------------------------------------
    YAML                           452            158            693         161655
    JSON                           396              1              0         155975
    JavaScript                       7             21           4513         123150
    TypeScript                     741           7913          19645          80869
    XML                             66           5208           1006          60935
    Java                           725           7380           2283          37863
    Scala                          272           3275           1423          25395
    CSV                            146              0              0          25335
    Markdown                        86           5019             21           9228
    SVG                             12              5           1749           9130
    HTML                            39             52              4           4073
    Maven                           16             61             87           1963
    SCSS                            47            380             85           1662
    Scheme                           5            121              0            864
    Python                          13            185             96            668
    Bourne Shell                    17             94            127            541
    DOS Batch                        2             30              0            268
    CSS                              1             17              0             81
    Properties                       9              0             24             60
    Text                             3              1              0             35
    TOML                             1              6              0             26
    Dockerfile                       1              8              1             19
    INI                              1              0              0              7
    SQL                              4              0              0              5
    -------------------------------------------------------------------------------
    SUM:                          3062          29935          31757         699807
    -------------------------------------------------------------------------------

An iPhone hitting someone in the head at 70mph could indeed kill them.

That’s a problem with lazydocker, not ghostty.

Maybe contribute to https://github.com/jesseduffield/lazydocker/issues/610 ?

We’ve had a lot of success with our Go library for iso8583

https://github.com/moov-io/iso8583

Deadcheck handles calculating the snooze durations for you. It could be a library as well.

I don't see how to configure anything but an interval (e.g. every N minutes) in checklyhq. Deadcheck allows you to expect check-ins at arbitrary times (e.g. 9am, 1:15pm, 3:15pm on weekdays).

https://developers.checklyhq.com/reference/postv1checksheart...

Systems always rely on something. PagerDuty has been very reliable for years and we use it for alerting, so relying on it more isn’t a big ask. I plan to support multiple integrations so you could get alerted from multiple streams.

No, you can get text, email, slack, etc alerts from PagerDuty without installing their app.

Yea I want to support other vendors. What do you use?

Yea I’ve setup multiple Alertmanagers that all check each other before. That setup is useful to detecting route failures between sites.

How are they triggering the alert when the dead man’s switch isn’t tripped in time?

Yea I’ve setup two alertmanagers that check each other before. It’s useful for multi site deployments.

Exactly. At Moov we rely on PD, so if they’re down we have bigger issues anyway. I plan to support additional integrations so a check-in could update multiple

Thanks, yea I’d like to support other vendors. Haven’t heard of Squadcast

I have https://github.com/adamdecaf/deadcheck/issues/12 tracking additional vendors

Edit: I'm open to a PR if you're willing. Curious, but would you use their delayed notification config to implement?

https://apidocs.squadcast.com/?version=latest#7742a9af-29fe-...

Yep. I looked at Cronitor and thought about using it, but direct to PD removed a step for us at Moov.

Thanks. We already rely on PD so preconfiguring the alert/snooze isn’t additional risk for us.

Yea the idea is that if your service doesn’t check-in then a preconfigured alert triggers.

There’s no crontab for banking days. Deadcheck also requires checkins within a delta of the expected checking time.

Deadcheck also doesn’t rely on your infra to alert.

It sets up expected check in times for an app/job. The job is responsible for checking in, but the alert will fire regardless of your infra.

Doesn’t require a start command and your infra can completely fail and you’ll still get alerted.

The idea is an app checks in after scheduled jobs, which extends the snooze

Yea, and you would delete the pending message. Good idea…

I’d like to learn more about switching compose to nix. We will hit a wall with compose at some point.

Buying the biggest Mac’s also lets developers run an electron app or three (Slack, IDE, Spotify, browser, etc) while running the docker-compose stack.

We’ve been using a hundred repositories and a hundred Go services in a local docker-compose setup that’s worked fairly well. CI runners can struggle if their disks can’t keep up with Docker.

It comes up that we should make a devprod for front end folks to make the backend abstracted more.

Overall a lot of people prefer local dev because it gives them access to the entire stack, lets them run branch images easier, and has better performance than remote boxes.

https://moov.io/blog/education/moovs-approach-to-setup-and-t...