dwelch2344

Realized I may as well put it on dockerhub. Published from the actions to `welch/docuhog`.

https://hub.docker.com/r/welch/docuhog

For when you really don't want to slog through the DocuSign portal (or shared credentials for developer sandbox)

This is the first cut (powered Claude, obviously) but seems to cover all my integration cases. Happy to collaborate on it

Tell me you haven't written a large library for a wide array of users (many of which you wouldn't trust with a potato peeler) without telling me

Except instead of corporations sneaking in your house to paint your room green during the middle of the night, it’s the corporations deliveratelu choosing to paint their lobby green + you just happen to frequent their lobby

Looks good. We’re publishing ours soon.

You should ditch nvm for Volta. It’s insanely better

Totally agree with this. "Kafka is terrible if you use it with poor practices" should be the title of this. It's totally clickbait targeting the "Database Inside Out" articles / concept, which if you read the most common 3-page high level it explicitly states you should be materializing up into other data sources / structures / systems / etc

To date, I've never written code that reads from a Kafka topic that wasn't taking data and transforming + materializing it into domain intelligence

Partner and I built a service to do sales attribution and commissions, ingesting data from Shopify / WooCommerce / etc. Works great for any sort of sales organization w hierarchy, but we’ve had success with network marketing / direct sales.

Spending nights and weekends, we scaled enough that we banked about $67k on the side in the first 8 months and then took used that as seed to go full time. 3 years later we’re still at it with a decent team and a ton of fun and cool tech

Interesting read. Not sure I agree, though not my area expertise.

The idea that we’re hitting full saturation, or that startups will have to push into market vs pulling sales from market gaps assumes that we’re reaching full saturation across the board. That the reach of everyone being online also means they’re all online in the same markets / products / verticals.

I’ve worked most my career consulting as a software engineer, primarily split in 4-5 business verticals. The giants in those spaces (hiring, healthcare, cosmetics, etc) have 8-15% market share. And there’s constantly turn over where people for whatever reason exit and return to the customer pool.

So while from an economic and academic standpoint this seems pretty solid, I have a hard time accepting it practically.

Again, anything I know about this kind of thing is peripheral knowledge, so very likely wrong. would love some insight :)

Make it part of your policy and very clearly disclose it up front while explaining the why. If they push back, concede by letting them pay for the non-refundable tickets up front then

Wrap it in a `keybase encrypt ...` and it's a pretty solid solution

I'd be interested to see how AWS' Elastic File System (EFS) compares (though I'd imagine it's not great, given it's mounted via NFS)

Pretty dangerous line of thinking when it comes to private keys for a wildcard cert on such a high traffic (and probably high value) target...

Also, there is no good reason to use 2 way encryption on passwords anyways. It goes against every security best practice.

I've spoken to a number of employees who have confirmed they are stored plain text.

I have considered those factors and am definitely concerned. However, consider the other side of the equation: a systems breach that leaves thousands (maybe even millions, given their size and 15 years of operation) of customers data being leaked, potentially leading to fraud and identity theft.

Who deserves to be protected? The organization that will not respond to the threat, or their innocent customers?

"Mobile-first, cloud-first"... I've used their cloud and even our .NET fanboys voted it off the island at our shop.

And mobile first? Do they even have a mobile offering? I mean, sure, the Slate is kind of cool. But doesn't your company need marketshare to say that you're "mobile-first"?

Looks pretty cool. One thing I don't get tho: How does the image upload work? Does it just base64 encode it and use inline images?

I'd like to agree here. IMO up-and-coming Clojure is an up-and-coming competitor to Scala. As a Lisp variant for the JVM, I'm a major fan of it.

Unfortunately I can't share any personal experience as the core of my work is in the Enterprise so I haven't had the right opportunity to present itself. But if you're coming from a mathematical background you should check it out

Get involved with your local community. Word of mouth is the best referral system when you're getting started.

Try using your personal network to find a local business / organization that is struggling with some piece of software / website. Or donate some work to a non-profit and ask them to spread your name around. Every successful project should bring you at least two more to work on.