Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ownagefool
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
31.
▲
by
ownagefool
6mo ago
Nobody really tries to get technical people to do the work. Like cool, it's a great idea and would potentially produce positive results if done well, but the roles pay half the engineering roles, and the interviews are stacked towards
32.
▲
by
ownagefool
7mo ago
In more practical terms:- 1. Users - your users table may not benefit by being ordered by created_at ( or uuid7 ) index because whether or not you need to query that data is tied to the users activity rather than when they first on-boarded.
33.
▲
by
ownagefool
7mo ago
To be fair, many human tests I've read do similar. Especially when folks are trying to push % based test metrics and have types ( and thus they tests assert types where the types can't really be wrong ). I use AI to write tests.
34.
▲
by
ownagefool
9mo ago
I haven't looked at pfsense UI, but you can happily hand out a prefix to a device, which can then hand out its own prefixes. I do it with my k8s clusters, which means the node themseves have enough IPs addresses to launch their own ro
35.
▲
by
ownagefool
10mo ago
https://renderapp.io/ A platform for digital asset management, review and workflow. Current features focus primarily on review of images aimed at automotive configurators. The problem is generic, however, our USP is we hav
36.
▲
by
ownagefool
10mo ago
Honestly, I think that's people reacting to the market more than it's the market reacting to people. If your average zoomer had the ability to get a job for life that paid comparably well by a company that would look after them, I
37.
▲
by
ownagefool
10mo ago
I suspect they were more referring to curmudgeons not patching. I was engaged after one of the worlds biggest data leaks. The Security org was hyper worried about the cloud environment, which was in its infancy, despite the fact their data
38.
▲
by
ownagefool
10mo ago
The thing about your bigco, the OPs and the post he's talking about, is it's all so abstract from money. You have two poles here. 1. The VC route, strikes gold, and never really needs to live with the reality of asking what an ROI
39.
▲
by
ownagefool
11mo ago
Sure. You tend to think about the edges of your application. 1. Router Tanstack Router: Supports runtime validation libraries such as z0d. So I have routes such as example.com/viewer/$uuid/$number, it should 400 if those ar
40.
▲
by
ownagefool
11mo ago
Agree wholeheartedly. Writing TypeScript is better than JavaScript, but the lack of runtime protection is fairly problematic. However, there are libraries such as https://zod.dev , and you can adopt patterns for your interfaces a
41.
▲
by
ownagefool
11mo ago
Jenkins has pros and cons. It's one of the few CI tools where you can test your pipeline without committing it. You also have controls such as only pulling the pipeline from trunk, again, something that wasn't always available el
42.
▲
by
ownagefool
11mo ago
Heh, me too. I think it's still just 2 poles. However, I probably shouldn't have prescribed motivation to latter pole, as I purposely did not with the former. Pole 2 is simply never adopt anything new ever, for whatever the motiv
43.
▲
by
ownagefool
11mo ago
It's not just Agile but the same applies to DevOps. DevOps is a culture. It can also be the specific subset of highly skilled individuals who were part of or an outcome of said cultures cross pollination. Today DevOps most often mean
44.
▲
by
ownagefool
11mo ago
The camps are wrong. There's poles. 1. Is folks constantly adopting the new tech, whatever the motivation, and 2. I learned a thing and shall never learn anything else, ever. Of course nobody exists actually on either pole, but the cl
45.
▲
by
ownagefool
11mo ago
The consequence of running ingress and DNS poorly is downtime. The consequence of running a database poorly is lost data. At the end of the day they're all just processes on a machine somewhere, none of it is particularly difficult, bu
46.
▲
by
ownagefool
11mo ago
The thing is, the core agile points from the manifesto are pretty much universally fine and can pretty much be boiled down to, "make changes fast, get feedback, gain more understanding faster". Pretty much everything that's b
47.
▲
by
ownagefool
11mo ago
Tech has built literal industries of people trying to stress you out, and they mostly don't have actual tech skills or the empathy that comes with them so back it up. For me, I usually try to avoid anything where the working practices
48.
▲
by
ownagefool
1y ago
Ordering System is a good example because you typically want both. Your base logic will probably exist in OLTP with joins and normalised data, and you'll generally have local on-device OLTP databases. Reporting on your Ordering System
49.
▲
by
ownagefool
1y ago
This is probably not really true. You wouldn't be publishing patient visits publically, the only folks that'd legitimatly see that record would be those which access to that visit, and they'd most likely need to know the time
50.
▲
by
ownagefool
1y ago
Meh. You probably shouldn't / don't need to use v7 for your Users table because the age of your User probably has limted to no bearing on the look up patterns. For example, our Steam and Amazon accounts are pretty old, but w
51.
▲
by
ownagefool
1y ago
Yeah, the argument apparently doesn't really grok how certificates are issued and why the changes exist. Manual long term keys are frowned upon due to potential keyleaks, such as heartbleed, or admin misuse, such as copy of keys on lot
52.
▲
by
ownagefool
1y ago
No disagreement. I was making space for a system like spanner whilst alluding to the fact it still needs to choose.
53.
▲
by
ownagefool
1y ago
To be fair, the idea of the tools being standardized behind a single command like golang is nice, but this is largely what it all comes down to. "Vite+ will be source-available and offers a generous free tier." I'm also a dev
54.
▲
by
ownagefool
1y ago
That's not multi-master in the typical sense, it's sharding, and done correctly, you shouldn't have any write conflicts because each shard should be strongly consistent within itself. Typically a strongly consistent (CP) syst
55.
▲
by
ownagefool
1y ago
I swallowed a shirt pin as a child. Went to hospital, x-rays, etc. Originally the set me nil by mouth and were set to operate, but the consultant overruled and luckily it passed naturally. (:
56.
▲
by
ownagefool
1y ago
Yeah, I agree with both you and the GP. There's a mess of commits that usually don't matter because mostly only the before and after level of an actual viable PR does, ergo I squash them. I'm cool with other reasonble approa
57.
▲
by
ownagefool
1y ago
Forget docker for a second. Suddenly you're in a team with 2-3 people and one of them likes to git push broken code and walk-off. Okay, lets make this less about working with a jack-ass, same setup, but each 5 minutes of downtime cost
58.
▲
by
ownagefool
1y ago
Sure, but a lot of this isn't super hard. I worked on FlexiScale, https://en.wikipedia.org/wiki/FlexiScale . The Architecture of IaaS provider doesn't need to look massively different from k8s. - Node Agent t
59.
▲
by
ownagefool
1y ago
PMs that can hire/fire are pretty common, but again how do they know who?
60.
▲
by
ownagefool
1y ago
Aye, It's a bit like saying you can't sell your code, because you wrote it in someone elses software. Writing a decent Dockerfile isn't hard, and keeping it maintained and working with new versions is still work and it's
More ›