2,708 karma · joined April 21, 2014
In theory it sounds great to say "just prevent construction of bad states," but this is a complex problem in professional software that involves coordination between programmers, designers, and product managers to get the UI features into the right place where preventing the construction of bad states doesn't lead to a frustrating UI experience for users. It's often far simpler, more pragmatic, and less complex in terms of coupling in both software and humans to just accept whatever state the UI gives you and figure things out somewhere else where you aren't bothering your users so much.
Ability to generate words describing emotions are not the same thing as the LLM having real emotions
In terms specifically of mass/energy conservation, as the other reply said, energy is borrowed from either the earth's rotation and/or kinetic energy from a counterweight at the end of the elevator up in orbit.
2. All tech companies I’ve worked at since around 2015 have completely standardized interview questions, sometimes also hosted in a GitHub repo where any employee is free to comment or even open a PR to request a change. Every candidate gets the same questions. This thing where “faang” interviewers just pull a random LC question out of their ass is complete insanity to me. An organized set of questions takes a senior engineer like a week to organize and commit to… And if your questions can be memorized and recited by rote memory and the candidate can do well on it without the proctor knowing, then your questions are BAD or your proctor is a moron.
3. I’ve never worked anywhere where I would describe the interview like this. Even the startup where I was the first engineer and there was no formal “test”, it was an hour long chat with the technical cofounder where he grilled me about coding skills and past experience/accomplishments. I won’t take a job if the interview isn’t asking me things that focus on my existing experience and skills, it’s a red flag about the company culture in general.
As for your “universal problem,” I disagree with fatalistic takes where you just throw your hands up and say “whatever shall we do” all the while YOU are the one benefitting from the system that cannot be changed. This is how simple-minded people think about the world.
Is the culture just so broken at these companies that it’s hopeless to expect people NOT to blatantly exploit the system for their friends? Why don’t people get fired for doing that?
I think both of us can be right at the same time though. Just because they had problems before the SoftBank acquisition as well doesn't necessarily make what I'm saying unreasonable. There was still sentiment in 2013 when SB closed the deal that regulators would not have approved of Sprint acquiring T Mobile [0], despite the struggles going on at Sprint at the time (that you describe). Sprint was definitely putting together a bid to acquire T Mobile, WSJ reported on it [1].
As you yourself said, Sprint was _dying_ at the time of the SB acquisition, but as far as large firms go, they were far from bankrupt yet. SoftBank simply twisted the dagger and then presented the corpse to congress instead of the dying patient.
[0] https://www.theverge.com/2014/2/4/5376824/fcc-chief-reported...
[1] https://www.wsj.com/articles/SB10001424052702303293604579256...
The reason their goose was cooked is because they previously were planning to acquire T Mobile, but SoftBank got back-channel info that it would never be approved by the anti-trust regulators. At the time they had Marcelo Claure running Sprint, basically a corporate "fixer" guy for SoftBank. So he ran the company into the dirt in order to make the merge feasible to regulators (e.g. - Sprint purchased a 33% stake in Tidal, the music streaming service. Or how they entered a partnership with bankrupt RadioShack after it got scooped up by PE, and decided it was a good idea to take over all the physical RadioShack locations and turn them into Sprint stores).
"Oh, whatever shall we do, our company is failing, you MUST let us merge with one of our primary competitors or we'll go bankrupt. No company at all is worse for consumers than a merged company."
"At times I was able to get the chat agent to give me what I wanted, but I had to be very specific and I often had to scold it."
You can't just half-ass a paragraph of disjointed system instructions into the user input and expect clean results, in my experience. You need to leverage the custom system instructions, give example responses if possible, and be very, very specific and direct with instructions. You need to explain the type of response you want, and you also need to describe any applicable constraints (or lack thereof) on the response content.
"When you are asked something, it is crucial that you cite your sources, and always use the most authoritative sources (government agencies for example) rather that sites like Wikipedia"
This is not sufficient to achieve what the author intends. It's written in a speech-like roundabout style (e.g. "it is crucial that"), and there's a typo right in the middle on an important word (than --> that). LLM can work around typos in most cases, but here it is vaguely possibly imo that this is what is causing it to continue citing wikipedia in responses.
"At times, the tool was too eager to please, so I asked it to tone it down a little: “You can skip the chit chat and pleasantries.”"
I have found in my experience playing with ChatGPT that this is just the completely wrong mental model to have of the tool in order to get what you want out of it. You have to treat it more like a prose-language programming tool, not like a person with emotions that you are conversing with...
There's gotta be some corollary here where, if an article is nudging you to do something, you should always think twice, because if the thing was so good and popular, then the article would not be a "nudge," it would be a report about how many people are already using the thing, and would be trying to give you FOMO.
What every HN commenter is replying to: "throw away your code"
--
I've written software professionally for 14 years and just last week I wrote code for ~3 days and then decided I was on the wrong track, and checked out main and made a totally new branch, spent ~1.5 days re-writing my feature in a totally different way. I had come to realize the new way would be easier to write, MUCH easier to test, and a bit more maintainable long-term. Nothing wrong with throwing away un-merged code if you decide that merging isn't the right decision, and feel you have learned valuable lessons to inform the re-write.
The logic makes zero sense, I'm sorry. It's still a "well, I wouldn't have to do X if you didn't do Y" mentality that completely and utterly shirks any sense of responsibility for one's or one's country's own actions. It's hogwash doublespeak used by BOTH abusers in messy interpersonal relationships, AND by international politicians playing realpolitik.
Big yikes here...
(good) Therapists are emotional intelligence coaches, they are NOT "shoulders to cry on," quite the opposite in fact.
I worked with a therapist doing CBT for a while, and have recently been working with a career coach. Neither of them ever let me "ramble" or "just let it out" with anything. They stop me and force me to unpack and separate the emotions from the thoughts from the reactions, and logically think through what is happening and how I can react in a more healthy way.