jpollock

5 ms·

1.
by jpollock 4d ago
"Years later the line of business asked for longitudinal reporting, cross-domain aggregation, and planning. The tool integrated with nothing, extended to nothing, had no underlying data platform, could not scale, and had to be rebuilt
2.
by jpollock 9d ago
Doesn't assembly allow devs to ignore speculative execution as well? You can place LFENCE(x86)/CSDB(arm) around code blocks, but you can do that in C too.
3.
by jpollock 13d ago
They will continue to breed, expanding territory unless there are predators. When they come across a culvert (or bridge), they will block it, eventually overtopping roads and washing them out.
4.
by jpollock 17d ago
If you can't look at the code, you need to trust interfaces to specify (and constrain) the implementation. The implementation needs to implement the entire interface and can't do anything not in the interface. Otherwise, you'
5.
by jpollock 22d ago
No, it's the wafer starts that are driving prices. Switching from Nvidia to custom doesn't change the constraints.
6.
by jpollock 1mo ago
I was in a high trust environment that didn't use dual auth on some things. They lost $250k to embezzlement. High trust is high trust until someone exploits it, and the likelihood of encountering an exploit (embezzlement, fraud, politi
7.
by jpollock 2mo ago
When you get into team development, doesn't it become the average? So, it's not just about your limits, it's about the team's average. Otherwise, you're the only one who can fix your code, and becomes a whole bus fa
8.
by jpollock 2mo ago
I know that as Kernighan's Law. Seems to be something that seniors learn over time. https://github.com/dwmkerr/hacker-laws#kernighans-law "Everyone knows that debugging is twice as hard as writing a program i
9.
by jpollock 2mo ago
There are also compliance reasons. SOX requires code review by a second party. If the reviews are automated, the development process isn't in compliance and that can get expensive in a hurry.
10.
by jpollock 2mo ago
It would be _extremely_ surprising if private repos were available via that contract. Corporations wouldn't use GitHub at all if anyone other than those given direct access had read/copy permission.
11.
by jpollock 2mo ago
I prefer the second. :) It's about the cognitive load and having to follow branches. The second version minimizes the cyclomatic complexity, taking it to 1. The reader doesn't have to keep the if statement in mind when reading thr
12.
by jpollock 3mo ago
I wouldn't think so. Most likely using a crass phrase to instill a feeling of urgency. Probably didn't work. Remembered though.
13.
by jpollock 3mo ago
Yes, but even then there are people who will ramp up faster. If the company is using Common Lisp, do you have the 6-12 months to wait for them to ramp up, or do you hire someone who has done Lisp before? That is downstream from the technica
14.
by jpollock 3mo ago
The programming language can have definite business impacts. It can impact hiring, salary costs (if the skill is rare), ramp-up costs (if it needs to be taught), etc. Even bus-factor comes into it.
15.
by jpollock 3mo ago
Programmers will write more efficient algorithms if their employers tell them to trade time-to-market for hardware cost. Previously, it was trade hardware cost for time-to-market. "Programmers" don't make this decision, the p
16.
by jpollock 3mo ago
This matching up with sliced data, either sliced by recipient, or sliced by sender, so it makes sense to have primary state with cool backups. Particularly if the state is race-tolerant. As long as event orderings are unimportant, or self r
17.
by jpollock 3mo ago
It depends on where your clients are, and where your servers are. You may have a lot of customers in a country and not want to host servers in that country (tax, regulatory, maintenance cost, etc.) RTT from Hyderabad to the East Coast USA i
18.
by jpollock 3mo ago
Yesterday. I was reviewing for an exam and came across a bug in the profs text. I took a screen shot pasted it in the prompt and asked. It initially agreed with the Prof, then checked it's work, revised and agreed with me, all while
19.
by jpollock 3mo ago
Isn't this the problem bazel's supposed to solve?
20.
by jpollock 4mo ago
If your data is naturally sharded (users) with writes happening within a single shard, parallelism becomes easy. The request is routed to the shard hosting the user's data and reads/writes locally. This makes scalability _much_ ea
21.
by jpollock 4mo ago
Glancing through the study, I'm curious about both sample bias, and the lack of formal measurement. I'm not an expert in this type of thing, not even an amateur. I'm poking holes to see what's left. "Participants we
22.
by jpollock 4mo ago
It's not a single payment failure, it would be multiple days, possibly even a week to 10days. This is why businesses should put in the effort and sign up for credit terms. Then it's an invoice, and you reduce this risk substantial
23.
by jpollock 4mo ago
There would have been efforts to contact them, but it would have been via their contact method, aka the email they set it up with. Common ways this happens? They are using a credit card to run their business with no backup payment method.
24.
by jpollock 4mo ago
Do any refactorings in separate reviews, and say things like "REFACTOR_ONLY:", with a rule that none of the code changes behavior. That makes reviews a lot easier. The review starts from "nothing should be changing" and
25.
by jpollock 4mo ago
Well, I think there are two things at play here. 1) As org size grows, it's the team's average quality that matters (so yes, large numbers). 2) Even with a single team, the velocity will increase to match the acceptable level of q
26.
by jpollock 4mo ago
Yes, that is what is required. Every dependency needs an internal owner and reviewer. Every change needs to be reviewed and brought into the internal repository. If no one is willing to stand up and say "yes this is safe and of accepta
27.
by jpollock 4mo ago
Faults are injected into the code at a constant rate per developer. Then there's the intentional injections. Auto-installing random software is the problem. It was a problem when our parents did it, why would it be a good idea for deve
28.
by jpollock 4mo ago
Code you ship vs tooling you use to build the code. So, the product vs everything that is needed on the way, but isn’t the core. CI/CD tooling, template population…. Things you write a use once/use few script for. I typically end
29.
by jpollock 5mo ago
You are communicating with future readers of the code. The presence of ConcurrentHashMap will lead future engineers into believing the code is threadsafe. This isn't true, and believing it is dangerous.
30.
by jpollock 5mo ago
A replaceable battery needs protection. One in the device gets protection from the device.

More ›