1,365 karma · joined July 7, 2015
1. https://www.congress.gov/118/bills/hres894/BILLS-118hres894i...
Humans love to pattern match, we find patterns in things that often have no real pattern. It is not uncommon in my experience to see patterns in code, label the code as not DRY, and attempt to DRY it up. If the "duplication" detected was, in fact, not a duplication but rather code that just happens to be similar, the abstraction will often go awry.
My rule-of-thumb is to prioritize maintenance over authorship. Am I writing this code in a way that makes it easier for future me or another programmer to change it, or am I optimizing for a sleek diff in my code review? I think our code can look like breadboards instead of a bespoke printed circuit board, we have compilers for that.
Perhaps if she was asked to make a website called www.thebibleisfake.com you might have a case for infringement of speech.
I think there is a difference here. It is not a prohibition in Christianity to create a website for a same sex couple, whereas producing an image of Muhammad is a prohibition in Islam.
I'd also argue that a wedding website for same-sex couples is not something that "contradicts biblical truth"; there is plenty of homosexuality in the bible.
I cannot think of a scenario where if I needed help with something I couldn't have a 5-minute conversation with someone.
Slack conversations I have several times a week: "Hey do you have a sec to help me? I can't seem to reproduce X bug" "Yea, wanna huddle?" "Sure!"
I don't know what new skills someone would have to learn in order to do that.
Folks building software can be more ambitious with the things they create, and it can become easier to plug in another software engineer to your team if tooling can make them more predictable in their output.
I see people here saying that increased efficiency is going to reduce their team's headcount which makes zero sense to me. I've never been on a team where there wasn't enough work to be done, it's usually a problem of too much work and needing to choose which is most important.
That being said, as someone who's been heavily using GPT-4 in their work and personal projects I feel like the gains are minimal. It's really great when I'm exploring an API I was unfamiliar with before, but for stuff I've been doing daily for years it's really not much help at all. Even places where ChatGPT shines, it takes some discernment to sift through the bullshit.
This just sounds like a thought-terminating cliché; what mundane things are you spending your attention on while writing code? Sure, there are times where you might be generating boilerplate, cool, you're paying for a fancy snippet library, except the snippets are potentially malformed so you should check them every time.
If I walked around the office calling my male co-worker by some random female name as a form of ridicule I'd end up on those cheesy videos they make you watch for sexual harassment training.
Anticipating maintenance is tricky; I had a scenario where a developer on my team created a utility function to abstract away some code that was being repeated multiple times in the same file. As an author that made sense because he was writing the same code over and over again, but down the line when we wanted a specific instance of this copied code to work in a slightly different way we ended up making the utility function handle the edge case.
Over time this utility became extremely hard to work with, because you weren't always sure if you made a change it wouldn't create a regression in other places it was used.
When we sat down and asked ourselves "Is this utility assisting in authorship at the expense of maintenance", the answer was clear. We removed it and put back the repetitive code. We felt good about it because in reality, 90% of the time we were interacting with this code we were doing it in maintenance mode, tweaks and small updates. When in maintenance mode I don't feel the strain of a specific part of my code being repeated, I'm only looking at a small subset of the code. Sure, if I need to author a new case in this code it might be a bit more wordy, but I think the tradeoff is worth it.
I am sure there are perhaps better ways to abstract things, or that we were doing DRY wrong, and our utility function could have been smarter, but I've seen this same thing play out over and over again and usually trying to make my abstraction better hasn't helped.
> I'm a part-time Real Estate investor, and I would never invest in a city that had a rental cap, since the point of investments is to make money, not start a charity.
This mindset is where these issues come from in the first place. Housing as become more and more an investment, and groups of people (immigrants, disabled folks, poor people) are not as good of investments, so they're avoided by private investors.
At the same time, private investors and builders are pushing back on tools that make the lives of these less profitably people easier (rent control, public housing).
From what you're saying, if I want to promote more affordable housing, I keep you away from it. Where's a profit in cheap housing/low rents?
What I mean by being concerned with deregulation that could hurt residents I mean things like gentrification, legislative reduction in rent-controls / tenants rights, relaxing safety laws / codes around what is considered a livable space. If that's NIMBYism then I am all sorts of confused :P
Also please correct me if I am wrong, I haven't dug too deep into YIMBY aside from surface level digging.