HN user

awalsh128

118 karma
Posts1
Comments37
View on HN

This is only an issue when you need to migrate services. I can't get into details but much of this isn't a problem anymore.

Yes votes were 144 D and 213 R in the house with unanimous yes (only one no) in the Senate. Right after 9/11 people were fine giving up with their rights pretty much across the spectrum. Granted Republicans more than Democrats. I think since then it has just been the status quo for every president since Bush. I hate it but it has been engrained at this point IMO.

This all reminds me of Makeshift Patriot by Sage Francis.

Same. I find myself much more productive. I do like coming in every once in awhile for the rapport and cultivating working relationships face to face though.

I don't think they are necessarily saying that. The data driven aspect is to connect users actually wanting or interested in something. The measure of this is the conversion rate, which is where the user actually clicks on the ad. You can also connect these with purchases from the ad buyer. The data driven piece is all the variables involved in developing functions that maximize this. At that point it is basically data science.

As a US citizen I just want affordable healthcare, housing, and a system that supports families. I think for the younger generation where this isn't attainable it causes a lot of unhappiness and leads to greater stressors. Also we are at a big low with faith in our political system across the pillars of government. I think for most of us we don't want it all, we just want our basic needs met without worrying about losing then tomorrow.

Whatever people think about Greenpeace I think it's a stretch to say they are a plant. They just lost a lawsuit recently and have to pay $660 mil for defamation against an oil company. It was a pretty ugly case.

Don't forget when you choose to opt-out but then start getting random spam from other businesses because they sold your email address. Also fun is when they send email anyways.

C# doesn't box value types and can be treated like an object semantically for things like generics.

IMO, we should just do away with nullability and use the optional/maybe approach as wrappers for potential values. Null shouldn't really exist ideally, especially in OO because it is a unit value and also the parent value for all objects. I appreciate nullability being introduced but it causes a fork in types by two branches at the top of the hierarchy in most cases and more conceptually just associates these optionals with this flawed concept.

The rulings coming out from the Supreme Court wreak of bias. This isn't uncommon and is checked by more of a balanced court but holy hell. I have no concept of jurisprudence and I can still see how blatantly partisan most of the rulings have been lately.

One of the things you can do is provide a guidance file like CLAUDE.md including not only style preferences but also domain knowledge so it has greater context and knows where to look. Just ask it make one and then update and change as needed.

I find these moments to be teaching a person to learn to fish. Not only tell them how to get the answer, but then ask questions to see if they put in the work needed before coming to you. If it persists, maybe address it directly in a one on one meeting. If it's systemic across different people, maybe there is a documentation or organizational problem. Sometimes it's training the person to help themselves, other times it's seeing things that are broken that prevent them from helping themselves. I see this especially in highly complex systems where there are large and multiple teams, and the person needs to be able to work across these areas.

I was not as surprised. It is a lot like the pattern in his previous term with people that he brought on and then had a fallout with and they became the enemy like cabinet members, VP, etc. This second term is markedly different in that he appointed only due hard yes men. I think the only difference is that Musk was very useful for his money and independent sway.

Sorry, this sucks as someone who has experienced this themselves. As a former customer support person, ask for a supervisor. Also be firm and serious without being rude or berating. Lastly never buy the "our systems are having trouble". That is support speak for "I have no clue, call back and talk to someone else".

I am an avid hiker now but grew up in the suburbs. Going out to the backcountry for the first time was a life changing experience for me and allowed me to connect to nature in a way I never did before. Having such beauty around me was the catalyst and disconnected me from everything. It gave me a real perspective of looking at my life as a whole. Appreciating the people in my life, my love for them and what my aspirations are. It isn't all perfect though. There are these little hells too cycling around my brain but they were there to begin with and something I am forced to face. As someone who has done mental health work I am allowed to sit with my feelings and discern them, which is a large part of the process. In the past two years I have asked myself, "what are you getting out of the time sinks on your phone?" Not a whole lot. I never go on social media unless occasionally to see what people are up to and I force myself to eat and sometimes wait for things without being on my phone.

I have found it nice in the coding area to bang out snippets or auto complete the pattern for things like data structures and flow control. Sometimes even debugging but there is a large amount of oversight to massage the code to correctness. It saves me time on the meneal things but the higher level comprehension is nowhere near there yet. As far as getting through documentation, summarizing, and interrogating, it can be much better, especially if you put all the documents in the chat scope so it can use it.

My take is that it won't replace us but our roles will evolve to leverage these tools more and more to achieve human ends. There are so many considerations to take into account like production stance, fallback, data integrity, mitigation, privacy, security. I think we are a ways from that. When AI can start solving production issues post mortem and requirements implementation, then I would say we have hit a milestone. With that said, new engineers should still need to understand the fundamentals of CS, systems and how to properly use a language.

My main gripe is this push of AI in everything without fully understanding the value proposition and if it would be useful in the given case. I mostly ascribe this to leadership who don't really understand it and think it will just solve all of their problems and vastly increase productivity. What's worse is when it gets passed down the chain from C-suite and ends up being a hot mess by the time you get a project because there is no true direction of how it will apply to your product. It takes good leadership and identifying genuine usefulness for certain products.