Skip Navigation

Posts
28
Comments
171
Joined
2 yr. ago

  • What? I've never played a game that limited the number of times I could install it.

  • And? It would take a trivial amount of effort to spin up VMs and install the game on each. If I immediately tear the VM down after, I'm sure my cost would be covered by free AWS credits.

  • The "Product Led Growth" crowd doesn't care about charging based on what things cost. They only care about what the buyer will tolerate. The "value metric" that pisses me off the most is per user pricing when the service doesn't incur costs per user.

  • I'm curious about using the same store for passwords and TOTP. Technically if someone gets screwed to your database, they have both your factors, yes? But I guess it does thwart someone trying to brute force your password.

  • Unless Reddit's TOS is vastly different from other social media sites, you keep ownership of your content and give them a perpetual license to host it on their site. That way, if you post something illegal, it's still your problem and not theirs.

    That being said, copying non-link content is technically copyright infringement from the original poster. It'll probably never amount to anything.

  • If I'm reading this right, it's a digested form of something else in those vegetables. So adding broccoli to toothpaste isn't going to cut it. (Although I'm sure some brand on IG is already manufacturing that)

  • I too want my query results in an object, but thankfully libraries like sqlx for golang can do this without the extra overhead of an ORM. You give them a select query and they spit out hydrated objects.

    As far as multiple DBs go, you can accomplish the same thing as long as you write ANSI standard SQL queries.

    I've used ORMs heavily in the past and might still for a quick project or for the "command" side of a CQRS app. But I've seen too much bad performance once people move away from CRUD operations to reports via an ORM.

  • Right. Even pay-once software can have a phone home component that disables it if the creator deems it. So really we're talking about old versions of software that just used offline license keys which were easily cracked.

    I honestly really like the Jetbrains model where they offer a subscription for continual updates but you also get a fallback version you can use forever if you decide to stop paying. It acknowledges that you aren't costing them money if you aren't getting the new updates.

  • While I don't disagree with the decision, I do think big tech companies are getting to have their cake and eat it too. They can simultaneously decline to host content, while also not being responsible for the content they do host.

    At the very least, I would like them to be responsible for content that was reported by users, reviewed by the company's employees/contractors, and then allowed to stay up.

  • Interesting. I'll have to find some docs and share it with my co-workers because they definitely don't use build-in refactoring. Thanks!

  • Jetbrains IDEs do a lot of indexing and caching so that operations that normally take a bit are faster. Full text search, find usages, identifying interface usage in duck types, etc.

    But the killer feature for me is the refactoring tools. Changing a function signature, extracting an interface, moving code to new files or packages, etc. I pair with folks who use VS Code and its a bit tedious watching them use find and replace for renaming things.

    I've never been able to benefit from an IDE in a way that make up for how much slower and more bloated they are.

    That does sound legit if you have resource limitations. Thankfully I've always worked for corporations that hand out MacBook Pros like candy. Normal day for me is having two Jetbrains IDEs open with Chrome, Slack, Zoom, and a dozen containers. Still runs smooth.

  • I'm not convinced that "strong pairing" is the best way to pair but even people who rail against agile ideology tell you that you're pairing wrong if you don't follow it precisely.

  • Code review is overrated and often poorly executed, most things should be checked automatically (review should still be done though)

    I think part of this is caused by the fact that a lot of people are bad at code reviews so they focus on things that a linter could have told you. Being able to read code isn't necessarily the same skill as being able to write it -- as evidenced by the knee jerk reaction to throw out any coffee we didn't write ourselves.

    I still create code reviews when I'm working on a project alone because it gives me a different perspective on the changes I've made.

  • Today I removed code from a codebase that was added in 2021 and never ever used. Sadly, some people are as content to litter in their repo as they are in the woods.

  • Please don't say the new language you're being asked to learn is "unintuitive". That's just a rude word for "not yet familiar to me".

    Yeah. I've written in six or so different languages and am using Go now for the first time. Even then, I'm trying to be optimistic and acknowledge things are just different or annoying for me. It doesn't mean anything is wrong with the language.

  • Not arguing either side, but I'd love to hear your reasoning.

  • They're all unpaid and probably classified as power users. So they have no employment protections.

  • And? My DNS provider shouldn't be leaking my information even if I immediately use the info they gave me to connect to the site.