Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
RaftPeople
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
91.
▲
by
RaftPeople
10mo ago
> I can, and have done several times, actually, for different systems. The reason I asked that question isn't to be argumentative, it's because, IMO, the answer to those types of questions are exactly what does not exist in t
92.
▲
by
RaftPeople
10mo ago
> Suppose you have a good commit 123 were all your tests pass for some project, you cut a release, and deploy it. And you've personally done this for a larger project with significant amount of changes and a longer duration (like
93.
▲
by
RaftPeople
10mo ago
> including "no development branches" Can you explain this comment? Are you saying to develop directly in the main branch? How do you manage the various time scales and complexity scales of changes? Task/project length
94.
▲
by
RaftPeople
10mo ago
> They are not, by definition. You provided proof for it yourself: you mention the "body of knowledge [...] above that", so they really aren't the topmost layer I said "shallow", not "topmost". >
95.
▲
by
RaftPeople
10mo ago
Fun stuff. I built a system like this for artificial life years ago (neural network was the brain). I'm curious how you handled the challenges around genotype>>>phenotype mapping? For my project the neural network was fairly
96.
▲
by
RaftPeople
10mo ago
> Are you really expecting an answer here? I'll answer anyway. Yes, and thanks for the examples, it's now clear what you were referring to. I agree that most of those are generally good fundamentals (e.g. wrong states, error
97.
▲
by
RaftPeople
10mo ago
> Once again, that's only true at the surface level. Can you provide concrete examples of the things that you think are foundational in software? I'm thinking beyond "be organized so it's easier for someone to under
98.
▲
by
RaftPeople
10mo ago
> Nah, those changes are only in the surface, at the most shallow level. Very strongly disagree. There are limitless methods of solving problems with software (due to very few physical constraints) and there are an enormous number of d
99.
▲
by
RaftPeople
10mo ago
> Could give examples of use cases where dense 3d packing is needed? (Say, besides literal packing of physical objects in a box? ) Not an answer, but something interesting on this topic: In a warehouse/distribution center, a dense
100.
▲
by
RaftPeople
10mo ago
I got the same vibe.
101.
▲
by
RaftPeople
10mo ago
> This individual was holding it as if it were a weapon When asked to clarify the communications officer provided the following evidence: "As you can see in this image the student is squinting a little bit, exactly what you would
102.
▲
by
RaftPeople
10mo ago
> The main difference therefore between error and warning is, "We didn't think this could happen" vs "We thought this might happen". What about conditions like "we absolutely knew this would happen regular
103.
▲
by
RaftPeople
10mo ago
> I can't think of any time obvious unintended behaviour showed up not caught by the contract encoded in tests Unit testing, whether manual or automated, typically catches about 30% of bugs. End to end testing and visual inspectio
104.
▲
by
RaftPeople
10mo ago
> In the real world I would not have a shared "money library" to begin with. If there were money-related operations that needed to be used by multiple services, I would have a "money service" which exposed an API and
105.
▲
by
RaftPeople
10mo ago
> There were some reasonable concerns. Using tables for both layout and literal tables removes semantic meaning The simple solution: <table type="layout"> (or "data")
106.
▲
by
RaftPeople
10mo ago
> At the SMB scale accountants are mostly paid to coach/pester/goade the employees to hand in the necessary paperwork in time. The perfect job for AI.
107.
▲
by
RaftPeople
10mo ago
I did the exact same thing.
108.
▲
by
RaftPeople
10mo ago
> But nobody really teaches the distinction between two passages that happen to have an identical implementation vs two passages that represent an identical concept, so they start aggressively DRY'ing up the former even though the
109.
▲
by
RaftPeople
10mo ago
> In software, optimizing for speed works best in cases where architecture has minimal relevance for product outcomes. The other consideration is the impact of low quality on the business. Generally, I find that cleaning up issues in
110.
▲
by
RaftPeople
11mo ago
> And boy to the people making the decisions NOT want to hear that. You are 100% correct. The way I've tried to manage that is to provide info while not appearing to be the naysayer by giving some options. It makes it seem like
111.
▲
by
RaftPeople
11mo ago
> While hardware folks study and learn from the successes and failures of past hardware, software folks do not I've been managing, designing, building and implementing ERP type software for a long time and in my opinion the issue
112.
▲
by
RaftPeople
11mo ago
> the main character is incapable of dealing with things inside him that he doesn't understand Exactly. To get to the point where he can really believe that the abuse was "not his fault" requires time and effort. If the
113.
▲
by
RaftPeople
11mo ago
> Yes, there may be interesting math, but I didn't mean "scaling LLMs", necessarily. Ya, I realized later that the LLM scaling part of my post sounded like it misinterpreted what you said when it was really a separate po
114.
▲
by
RaftPeople
11mo ago
> This is simply a scaling problem, eg. thousands of single I/O functions can reproduce the behaviour of a function that takes thousands of inputs and produces thousands of outputs. I think it's more than just scaling, you ne
115.
▲
by
RaftPeople
11mo ago
“Mr. Mainway, this is simply a bag of jagged, dangerous glass bits.” “Yeah, it’s broken glass. It sells very well, you know. We’re just packaging what the kids want.”
116.
▲
by
RaftPeople
11mo ago
Thanks for the response, it was very informative. > Frege's tension of coextensivity (A = A and A = B) I googled and now reading up on this one. I really enjoy how things that seem basic on the surface can generate so much thought
117.
▲
by
RaftPeople
11mo ago
> I have never seen a Money type nor anything like DEC64 in a real commercial system, its all floats or ints/longs for pennies. I've been working in ERP land for a long time working with many different commercial systems of d
118.
▲
by
RaftPeople
1y ago
> that the original mainframe hardware has likely been virtualized at this point The as400 is a mini-computer, the high end of this line overlaps the low end of mainframe. When I did some consulting work out there many years ago, they
119.
▲
by
RaftPeople
1y ago
It's a network of high end as400's, the software is custom. They've burned multiple 100's of millions of dollars on multiple projects trying to re-develop and move off as400's, but they just pulled the plug on their
120.
▲
by
RaftPeople
1y ago
Slight tangent but you seem well informed so I'll ask you (I skimmed Stanford site and didn't see an obvious answer): Is the assumption that there is internal state and the rulebook is flexible enough that it can produce the corre
More ›