Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)JD
Posts
2
Comments
244
Joined
2 yr. ago

  • My partner and I live in Silicon Valley and it's cheaper for us to rent a car when we need it than to own one. We'd use it maybe twice a month so rentals just make more sense. We're moving to San Francisco soon though and at that point we'll likely never own a car and just transit everywhere.

  • Something people don't tell you is you can file federal and state taxes at completely different places (they're 100% separate anyway so it really doesn't matter). I did this one year using freetaxusa for federal, and some other tax software that did state for free but charged for federal.

    This next year though I'm hiring a CPA because my shit has become complicated.

  • Never thought writers would have to deal with that too, but i guess everyone thinks they should write a book now. Software engineers experience the same shit. "It's Facebook, but inconsequential feature that no one will use". I've started quoting people twice my hourly rate from my full time job and it's gotten it to largely stop.

  • This is entirely a cultural problem if that's what you experience with remote employees.

    My company is remote-first with WeWorks for those who want them. Every meeting 90% of people have their cameras on, and the other 10% are either attending to something more important than the meeting or just not feeling it that day. No one questions them or gets onto them because we're not children.

    If many people regularly have their cameras off in meetings then maybe your meeting isn't worth their full attention, and they're working on something else. Not every meeting needs everyone to be there. I'd wager part of the reason my company doesn't have this problem is we have an extremely low meeting culture. Impromptu meetings/discussions are encouraged and we often Slack huddle for 5-10 minutes when needed which cuts out a lot of the bullshit.

    At my prior job we accounted for 2 hours a day of meetings when planning and it was a fucking drag. Now I have 3 1/2 hours of recurring meetings per week, with a sync for new projects/initiatives every few weeks. I get so much more done every day because I'm not listening to an endless stream of information which should have been an email.

  • LLMs aren't gonna replace anyone's jobs anytime soon. Their true power is making people even more productive.

    I keep getting told that AI is gonna replace devs. While copilot at work is fucking awesome to use, it's also created the scenario where AI doesn't have to compete with devs anymore, it has to compete with devs who can use an AI to automate the easy stuff and do even more impactful work. You can apply this to basically all jobs. So until the LLMs can outperform a human + AI we're gonna be fine.

    Not to mention until an AI can coax out what the fuck anyone even wants us to build in the first place I think we're safe.

  • Fair enough, but as someone who has worked closely with the Decky Loader maintainers and contributed my own stand alone plugin I get it. We basically all have day jobs as devs and it can be mentally taxing to do more PRs at home. Not to mention sometimes there's just not enough time in the day, and I don't even have kids.

    Maintainers are ultimately volunteers doing work with hundreds of dollars an hour for free. I've had some PRs take 20+ days to be looked at, it's just how it goes.

  • California. Highest taxes in the US, yet we generate 14.2% of the country's GDP despite being 11.7% of the population. We have an economy the size Germany (who has the world's 4th largest economy) with 46.4% the population.

    People talk shit about the state, how awful it is, etc, and while we do have many problems we're doing pretty damn well all things considered. If we get housing and healthcare fixed (both active efforts by our government) we'll be in an amazing position as a state.

  • Eh, it's really not that much money to get a half decent set. Learn to sharpen/hone a knife and learn how to use a knife properly and you can make even cheap knives last basically forever. Babish has a <$100 knife set that's serviceable as a professional set.

    I'm very into cooking and have a $700 set of Wüsthof knives and they're awesome to use, but 100% unnecessary. They'd be no better than a dollar store knife if I didn't learn to take care of them. So many people drag knife edges sideways on cutting boards, cut on improper surfaces, cut in ways that dull the edge quickly, and then throw them in the dishwasher. Then after a year of not sharpening them replace them for more than the cost of a good sharpener.

    With proper care/use and almost daily cooking I sharpen my chef's knife once a month, and my other knives once every few months. For $50 you can get a sharpening system with a guide that makes it almost impossible to fuck up and you'll never pay for knives again.

  • I mean the whole concept of the fediverse is inherently going to attract the more paranoid of people who don't want to have big tech down their throat 24/7. The people most aware of this are those that work in/adjacent to big tech, and have enough understanding to be genuinely concerned about the state of the internet. Not that you have to be in tech to use/enjoy the Fediverse, but Lemmy is inherently inconvenient and less content rich than Reddit so it's going to create more niche/less diverse communities who have common interests.

    Tech also has a very large trans demographic compared to the general population, and you can see that reflected on Lemmy too. The whole platform is largely going to reflect tech demographics until it is well known by the general public.

    I'm just glad most people here are nice and willing to have open discussions. I've seen more threads of people disagreeing and reaching common ground than anywhere else.

  • I feel the exact same way, except that id recommend it for many of the things you've criticized it for. The gameplay loop is pretty unique, and the build up to cooking every night implements a level of strategy to the preparations you have to make leading up to it including what fish to catch and how you invest your money.

    The game feels all over the place, but in a really good way. It's not just a repetitive, "fish, cook, repeat". There's a million random ass things that get thrown into the mix which is a complete 180 compared to most games made now. It's good because it doesn't really follow the traditional rogue-lite formula that we've come to know. It gives off the feel that the developers created the core game, (fish, cook, repeat) and then along the way took a bunch of, "wouldn't it be cool if we did x" idea they had and threw it in there to mix the game up. It's a super nice game to play while relaxing as the stakes are low, the story doesn't require immense focus to follow, and you're ultimately just fucking around under water as on overweight diver named Dave.

    It feels a lot like a game made for those that don't play many games, and I think that's why it's doing so well.

  • A low end laptop, maybe, but anything you need power to do would be rough given the thermal limitations and comparatively weaker processor in the iPhone. I do agree that most could get away with a docked phone instead of a desktop if the implementation was good enough.

  • From what I've seen one dude is salty and everyone else (including myself) is happy to have your contributions! I don't necessarily agree with you on everything you post, but you're respectful and actually back up what you say. I respect that a hell of a lot more than someone who I'm in complete agreement with, but plugs their ears at the first sign of pushback.

  • Just because you're not writing high performance software doesn't mean it shouldn't be a consideration. Sure, I'm not gonna micro-optimize memory when I'm writing an API in Python, but that doesn't mean I'm not going to write it efficiently.

    If I have to store and then do lookups on some structured data I'm gonna use a hash table to store it instead of an array. If I need to contact a DB multiple times I'm only gonna close my connection after the last query. None of this is particularly difficult, but knowing when to use certain DSA principles efficiently falls pretty firmly into the computer science realm.

    If you need someone to hyper-optimize some computations then a mathematician might be a better bet, but even those problems are rarely mathematician level difficult. Generally software engineers have taken multivariate calculus/differential equations/linear algebra, so we're decently well versed in math. Doesn't mean we don't hate the one time a year we have to pull out some gradients or matrices though.