I think there's more to your sibling's taxes than property taxes. The data tell the opposite story - WI property taxes are higher than TX ones, at least if we look at the medians:
As someone living in Fort Worth and making good money as a Staff SWE, I got a tax refund this year. It was due to paying interest on my house, but still.
I'd recommend asking your sibling see if they qualify for the homestead exemption, it's significant. You or they can check if they're using it and see their exact property taxes here:
Texas property tax rates are some of the highest in the country. Should be higher than Wisconsin.
The difference here is really more of an indicator of property values in the respective areas. In major metros in Texas, you're looking at ~2%+ tax rates, which is infact higher than Wisconsin, even in the metros there.
> As someone living in Fort Worth and making good money as a Staff SWE, I got a tax refund this year. It was due to paying interest on my house, but still.
If you paid more in property taxes, that would indicate you can take a larger federal tax deduction... so, if anything, a tax refund implies you paid a lot in local property tax. Either that, or a boatload in interest (or, both). Neither is indicative of local property tax being low.
It can be hard enough for humans to just look at some (already consistently passing) tests and think, "is X actually the expected behavior or should it have been Y instead?"
I think you should have a look at the abstract, especially this quote:
> 75% of TestGen-LLM's test cases built correctly, 57% passed reliably, and 25% increased coverage. During Meta's Instagram and Facebook test-a-thons, it improved 11.5% of all classes to which it was applied, with 73% of its recommendations being accepted for production deployment by Meta software engineers
This tool sounds awesome in that it generated real tests that engineers liked! "zero human checking of AI outputs" is very different though, and "this test passes" is very different from "this is a good test"
Good points regarding test quality. One takeaway for me from this paper is that you can increase code coverage with LLMs without any human checking of LLM outputs, because it’s easy to make a fully automated checker. Pure coverage may not be super-interesting but it’s still fairly interesting and nontrivial. LLM-based applications that run fully autonomously without bubbling hallucinations up to users seem elusive but this is an example.
Many iOS users use the Messages app to send and receive text messages which can be trivially backed up to iCloud but not other cloud storage solutions. Among people who text (common in the US) I'd imagine there aren't many iPhone users with less than 5GB of data stored in iMessages
That said, you can back iMessages up to a computer and back up files on your computer. You just can't restore iMessages to different Apple devices like this, but now we're talking about minor grievances to a really tiny segment of the population
> you'd be an idiot if you don't mass apply using your resume. Everyone does it, so you have to as well.
I've been on the receiving end of mass applications. If you stopped justifying your spam behind "everyone does it" (no they don't) and started tailoring your applications, leaning on your network (or building one up) you may need a lot fewer.
I have never mass applied, so I may seem idiotic to you. But even during the times I quit a job before looking for another, I've never been on the market for more than 2 weeks.
Georgia the country has about half the land of Georgia the state in the US, and Georgia the country has about half the population of Atlanta alone (even less population when compared to the entire US state of Georgia). I think that huge difference in popularity contributes largely to why "Georgia" often refers to the the US state on this site
I think a lot of really smart people end up claiming something like "this whole system wasn't designed properly, we can do it way cleaner if we redesign it from the ground up" but it's always a trap. Incremental improvements take less time, can be more easily understood, are safer to deploy. But a lot of those really smart people have perfectionistic tendencies that cloud their judgement, and nobody can imagine all the different paper cuts that will get in the way of their beautiful vision. And thus, the new technical debt (to someone else) is written
Perhaps something that could you help is adding an H1 to the readmes like "This project is finished, not being developed", with some explanation like "Unless you found a security vulnerability, your issues and PRs may be ignored or receive delayed responses. Feel free to fork this repo if needed. Please do not ask if this is dead."
This clarifies your stance so well that people acting in good faith won't bother you, and anyone who does bother you very likely isn't acting in good faith - easy to ban.
Plus, when you see someone ask questions about your project and interpret them as "a bulleted list of the reasons I suck", it implies that on some level you think "I suck because I'm not giving these projects more of my time". Giving that kind of disclaimer might help you move away from that mindset, and instead feel more at ease with yourself. Your contributions should be celebrated (as the person with those bulleted points did!), and anyone acting in good faith can appreciate them and fork if needed
Perhaps it'd be good to have a template that open source projects can use to set expectations, or a badge or something. Based on your suggestion it could be something like
I consider this project
- actively developed
- a toy
- finished
- still interesting to me
- no longer something I expect to progress
I will / will not review PRs [unless they are Security / some category].
Your best option if you would like changes is
- raise a PR
- ping me
- fork it
- use a different project
- pay me
My attitude to forks is
- The more the merrier
- A necessary evil
- I'd like to avoid them for this project if possible
- Not allowed by the license
I've seen apps break in prod where third party libraries had array accesses on indices that didn't exist, or dereferenced nil pointers, in goroutines they spawned. And those aren't the only ways to cause a panic without ever calling the panic function.
Third party libraries have bugs sometimes, and other times our usage of them can create bugs. Nothing like a SIGKILL or anything malicious. That's just the way things are and will be. And breaking down like this in dev can be fantastic!
But when a once in a blue moon issue crops up in prod and all other connections are dropped, the fact that a simple defer+recover couldn't have been preemptively placed on all goroutines is a huge nightmare. I'd even take a "you can add defer+recover for any goroutines created further in this callstack" - it's rare that libraries spawn goroutines, I'll already know which ones to trigger that behavior on
> But when a once in a blue moon issue crops up in prod and all other connections are dropped, the fact that a simple defer+recover couldn't have been preemptively placed on their goroutines is a huge nightmare
Yeah, this is one of the weird things, to say it mildly, that Go does that is hardly mentioned anywhere. Most people don't know about it until they themselves first encounter the nightmare bug similar to what you said.
Wrapping every third-party library in defensive code doesn't make a lot of sense since this isn't the most dangerous kind of bug. To make a one example of a million: a third-party database library that corrupts your database is infinitely more dangerous and that there's no form of wrapping that will save you.
Bad code is bad code. Bugs are bugs. This issue is not a major source of problems in Go code.
> This might mean you can't use TheTradeDesk and Google Adsense en-masse for example. Basically, as of today, a lot of price discovery is now automated by a majority of companies using a handful of vendors for this.
IANAL but this seems incorrect. Price discovery is one thing, being contractually obligated to keep prices at a certain level 80% of the time is another. A court can make a ruling about that 80% number in the contract without saying anything that impacts one's ability to discover the prices competitors charge
TradeDesk has algos that set bids (supply side), rather than set prices (sell side). Maybe SSPs have algos for setting floor prices that would be affected.
https://www.propertytax101.org/propertytaxbystate
As someone living in Fort Worth and making good money as a Staff SWE, I got a tax refund this year. It was due to paying interest on my house, but still.
I'd recommend asking your sibling see if they qualify for the homestead exemption, it's significant. You or they can check if they're using it and see their exact property taxes here:
https://www.tax.tarrantcountytx.gov/search
reply