throwawaylala1

7 ms·

1.
by throwawaylala1 3y ago
looks like they're crypto guys so there's that
2.
Ask HN: Is our society equipped to deal with modern social networks and tech?
2 points by throwawaylala1 3y ago|1 comments
3.
by throwawaylala1 3y ago
Any time something is adopted as broadly as JavaScript it's going to be a mess. Even outside the world of computing. Take... city planning. Cities are a mess. In fact human civilization is one big freakin' mess. Wouldn't it b
4.
by throwawaylala1 4y ago
> Also, since you’re probably deploying containers to production, it’s useful to have a similar environment for local development so that you know what will actually happen in production. This such a complete and utter lie and I'm s
5.
by throwawaylala1 4y ago
I mean it's a pretty simple concept. Your frontend team needs an API call that retrieves only friend requests with user names/avatars because the current API call is too heavy. Normally they'd go to the back-end team and ask
6.
by throwawaylala1 4y ago
> You can turn off recommendations Not really. When you turn off recommendations, the app icons are hidden but the space for recommendations stays there! Yes, just a big ol' block of whitespace with a prompt to turn recommendations
7.
by throwawaylala1 4y ago
Wow Snowflake absolutely crushes these benchmarks. Anyone know why? I don't know much about this space.
8.
by throwawaylala1 4y ago
Wouldn't you lose more just by sitting on cash? Even now?
9.
by throwawaylala1 4y ago
Right, I was just pointing out the flaw in the parent commenter's statement. You can't do "code version is tied to your database version" - that's just not a thing.
10.
by throwawaylala1 4y ago
You can't restart all of your web services atomically. What happens if two web services are running two different versions for a couple seconds?
11.
by throwawaylala1 4y ago
> More practically > event sourced architecture You must be joking. Please tell me you're joking.
12.
by throwawaylala1 4y ago
I use VIM and didn't even know ACME editor existed. Keep building strawmen, I'll be building software.
13.
by throwawaylala1 4y ago
Which didn't answer my question at all. Adding more structure to the AST with @param/@return/whatever doesn't make for better documentation. It's useless crap in a real world scenario.
14.
by throwawaylala1 4y ago
I have. My editor also gives me documentation for every function that I need. Plain text is more than enough for that use. What kind of function documentation are you reading inline lol? Does it have like 30 function arguments?
15.
by throwawaylala1 4y ago
So here's an example of the string package: https://pkg.go.dev/strings In what way would the JavaDoc @param/@return/etc annotations actually help? What Godoc has is more than suitable for the vast majority of
16.
by throwawaylala1 4y ago
This is why I said it's hard to succinctly explain. Non-programmers and bad programmers can't tell the difference between Go and Python (for example) in this context. The actual difference is very very significant.
17.
by throwawaylala1 4y ago
Single Point of Failure. LOL.
18.
by throwawaylala1 4y ago
You may be right, but... and maybe I'm being naive here... if HN can do it, why can't local social networks? The amount of people in the network is even smaller than HN. I suppose the problem is finding good moderators that keep t
19.
by throwawaylala1 4y ago
> The best way would be exporting docs from your codebase, and have all documentation related artifacts expressed alongside the code I LOVE Golang's approach to this [1]: - Documentation generation from code is built in to the lan
20.
by throwawaylala1 4y ago
We have one too but it's overrun by jerks. Lots of bickering and ganging up on people.
21.
by throwawaylala1 4y ago
Sure. We could also not use a container registry. Or resource management. Or liveness/readiness probes. For the database we could use RDS and take the latency/$$$ overhead. For file storage set up a separate EBS volume or whatever
22.
by throwawaylala1 4y ago
This is a tough one. I wouldn't worry that much about employability. If you're honest, hardworking, and love writing software then I don't see any issues there. I'm sure you've solved enough hard interesting problem
23.
by throwawaylala1 4y ago
I'd rather not say but it wasn't anything mind blowing. It was a B2B thing with a great UI in the early 2010s. You'd never have even heard of us. All of this predated the popularity of k8s. Docker wasn't really a thing.
24.
by throwawaylala1 4y ago
Yea. We had a monorepo. The whole thing was one big webapp. Even our background workers ran in the web app. Oh yea, that's right. I can feel the cringing just writing that! So like if we had an expensive background operation, our web a
25.
by throwawaylala1 4y ago
If you're truly interested in being enlightened then do the work. It's not up to internet strangers to refute your painfully uninformed assertions in detail. That's what education and work experience are for. You simply can&#
26.
by throwawaylala1 4y ago
I've worked at 3 organizations that adopted k8s. This all happened over quite a long period so I saw what k8s adoption looked like at varying stages of k8s development. k8s gets shit for one very simple reason: it forces teams to deal
27.
by throwawaylala1 4y ago
The miscommunication is in your mind. Every software out there has defects. Bugs, performance issues, UX issues, etc. To assume that anyone in this thread actually means that submodules have no defects whatsoever... well... that's just
28.
by throwawaylala1 4y ago
> You were elaborating on the comment, weren't you? And that comment was quite vague too. What was vague about that comment? > The difference between "what are uses and misuses" and "what is good and bad" is n
29.
by throwawaylala1 4y ago
It was a response to a comment, not the OP. There is nothing "bad" about submodules. They do what they were intended to do very well. They are often misused because people don't take the time to understand how things work (ev
30.
by throwawaylala1 4y ago
Exactly! Submodules are a tool within a toolkit. Learn the toolkit, learn the tool, and then decide whether or not it'll solve your problem.

More ›