HNHacker News
TopNewBestAskShowJobs

okamiueru

2,285 karma · joined December 10, 2011

submissionscomments
okamiueru··on FCC: TikTok is unacceptable security risk and should be removed from app stores
I wouldn't really say that the nationality is all that important. Just what my prejudices say. CCP tend to stifle opinions they dislike. Russia tends to fund divisiveness in the west. Facebook and US companies in general do whatever makes them money entirely devoid of any moral compass. Google sometimes can be gamed due to either carelessness or ineptitude. In any case, and as mentioned, mostly prejudice, is the answer to your question.
okamiueru··on FCC: TikTok is unacceptable security risk and should be removed from app stores
My concern seems to be different than that of most expressed here. Companies collecting too much information is a problem, sure, but that's not what deeply worries me when it comes to social media generating/consuming platforms like Facebook, TikTok and YouTube. Especially those that algorithmically decide what to show users.

Foreign countries controlling what information a coming generation is exposed to is IMO much more concerning than collecting and profiling (of course also troubling, but a slightly different league). There is little oversight into what bubbles are formed, who is fed what, etc.

Want to create division in a foreign country? What better place to start than on social media and malleable kids.

This applies equally to TikTok as Facebook, for different reasons. I don't trust TikTok because of CCP, and Facebook because everything is for sale.

okamiueru··on Google reveals plan for big change to Gmail. 19 days to object
That sounds truly horrifying. I won't presume you want a suggestion, but after switching to protonmail, the feeling of using a product rather than being one, is refreshing.
okamiueru··on Google reveals plan for big change to Gmail. 19 days to object
> no matter how many times I unsubscribe or mark email as spam I still get bombarded.

I agree that it shouldn't be necessary, but, why not set up a filter to block that sender?

okamiueru··on Gmail users “hard pass” on plan to let political emails bypass spam filters
What's the ussje with the calendar? How Google parses your email and creates events is convenient, but fair enough. Perhaps the ability to easily share calendars with others? What are some things you are wishing it had?
okamiueru··on I've been abusing HTTP Status Codes in my APIs for years
Also, the OP article does explain well what could cause this misunderstanding. HTTP resource nouns shouldn't ever be "guessed". The resource either exist or it doesn't. And if it exists, it either has a data, or it doesn't.

404: it doesn't exist 204: it exists and has no data to parse.

okamiueru··on I've been abusing HTTP Status Codes in my APIs for years
I really enjoyed that SO thread, and your answer. In my opinion your take is correct, to the extent that it is fascinating that it is a controversial topic. The majority of people, (and by people, likely limited to software developers), seem to not fully understand HTTP status codes. This is of course fine, the fascinating part is the extent they insist they do. Whenever the majority, in any technically field, opine something different, I assume they are right, and I've missed something. But having designed APIs for years, I can safely say that it doesn't apply here.
okamiueru··on Assassin’s Creed Liberation delisted, unplayable even to owners starting Sept 1
This seems like a what should be a non-issue, and good PR for very little effort.

Push an update to steam where DRM has been disabled. Arguably DRM has only ever inconvenienced legitimate users. Explain the situation saying it has reached end of life, so DRM protections will be disabled.

The developer/publisher gets this in return: - Good PR - No DRM server costs - Continued sale (/or make it PWYW and give proceeds to a cause).

okamiueru··on Kubernetes is a red flag signalling premature optimisation
I should perhaps have clarified, but the 10-15 are not self maintained services. You need nginx for routing and ingress, set up cert-manager and other ingress endpoints are automatically configured to have TLS, deploy prometheus, which comes with node-exporter and alert-manager, deploy grafana.

So far, we're up at 6 services, yet still at almost zero developer overhead cost. Then add the SaaS stack for each environment (api, worker, redis) and you're up at 15.

okamiueru··on Kubernetes is a red flag signalling premature optimisation
That is probably a good idea for many startups. However, once you get into the world of audits and compliance certifications, things become a lot harder. But, but then again, at this point, I suppose it is easy enough to transition to some managed hardware.
okamiueru··on Kubernetes is a red flag signalling premature optimisation
There is nothing stopping you from hosting your own OpenStack, managed k8s, and all that, on your own hardware. You would need a good reason to not let someone else deal with all of this though.
okamiueru··on Kubernetes is a red flag signalling premature optimisation
Using the helm charts from the community is arguably still doing it alone. There isn't anything back and forth. It's just the right tool for the right job. But, this starts being about language and semantics. Like saying that following a best practices on how to configure nginx isn't doing it alone, because someone else wrote that. Helm charts just very often expose what needs to be configured, and otherwise follows those best practices.

As for debugging. You do have a point that it becomes more difficult. But, this also holds true for any of the alternatives discussed her (lambdas, terraform). I'd argue that when it all comes down to it, that because you can spin up the entire infrastructure locally on things like minikube, that it makes it many times more easy to debug than other cloud-provider-only solutions.

okamiueru··on Kubernetes is a red flag signalling premature optimisation
I'd argue that using helm charts is the exact opposite of NIH. The things that take time are not the stack themselves, but the software and solutions. K8s just makes the stack defined in code, and written and managed by dedicated people (helm maintainers) as opposed to a bit "all over the place" and otherwise in-house, directly using cloud provider lock-in resources.

I'm sure there are plenty of use cases where that makes sense, and is a better approach. But, I disagree that k8s suggests a NIH-mindset.

okamiueru··on Kubernetes is a red flag signalling premature optimisation
> Prometheus, grafana

In short. Prometheus is a worker that knows about all your other services. Each service of interest can expose an endpoint that prometheus scrapes periodically. So the services just say what the current state is, and prometheus, since it keeps asking, knows and stores what happens over time. Grafana is a web service that uses prometheus as a data source and can visualize it very nicely.

Prometheus also comes with an Alert Manager, where you can set up rules for when to trigger an alert, that can end up as an email or slack integration.

They are all very useful, and gives a much needed insight into how things are going.

okamiueru··on Kubernetes is a red flag signalling premature optimisation
It seems many are focused on the time estimate. That was in creating the overall solution. About two months was to set up the infrastructure mentioned.

These often get developed side by side. GitLab, unit tests, api-server, nginx, cert-manager, deployments, integration tests, prometheus, metrics in services, grafana, alert-manager, log consolidation, work services and scaling, etc.

Just spinning up a cluster, nodepool, nginx, cert-manager w/let's encrypt cluster issuer, prometheus, grafana, can easily be done in a day. So, time estimates kinda depend entirely on what you mean by it.

Spinning up promerheus and grafana with automatic service discovery: one day. Making good metrics, visualizations, and alerts: everything from a week to a month or two. So, take the time estimates with a grain salt.

okamiueru··on Kubernetes is a red flag signalling premature optimisation
Any startup that knows what their product is and are done with PoCs, should be able to deal with the consequence of succeeding, without failing. Scaling is one of those things that should be in place before you need it. In our case, scaling was a main concern.
okamiueru··on Kubernetes is a red flag signalling premature optimisation
Ah, I see. Well, lambdas are also a nice tool to have, but it certainly do not fit for all applications (same as with k8s). I'd also point out that lambdas replace a rather small capabilities of k8s, and the type of systems you can put together. You would end up needing to set up the rest either through a terrible AWS UI or terraform. Neither of which I find to simplify things all that much, but perhaps this is a matter of taste.

In our case, the workers were both quite heavy in size (around 1 GB), and heavy in number crunching. For this reason alone (and there are plenty more), lambdas would be a poor fit. If you start hacking them to keep them alive because of long cold starts, you would lose me at the simple part.

okamiueru··on Kubernetes is a red flag signalling premature optimisation
That's seems like a very negative take in my opinion. This 'simpler operational tech' would still need to be able to scale, correct? If you think that there is a good and easier way to deploying 10-15 services, all of which can scale, and all of it defined in rather neat code, to be anything but "simple operational tech", then I believe you are confusing "solving a complex problem", with "simplifying the requirements of a complex problem". The latter of which has been stripped of many important features. K8S isn't anything magic, but it certainly isn't a bad tool to use. At least not in my experience, though I've heard of horror stories.

That does remind me that when that employee started, the existing "simple operational tech" was in fact to SSH into a VM and kill the process, git pull the latest changes, and start the service.

The only way you can solve the actual problem (not a simplified one) would in my opinion either be k8s or terraform of some kind. The latter would mostly define the resources in the cloud provider system, most of which would map to k8s resources anyways. So, I honestly just consider k8s to better solve what terraform was made for.

I'm sure the "simpler operational tech" meets few requirements for short disaster recovery. Unless you have infrastructure as code, I don't think that is possible.

okamiueru··on Kubernetes is a red flag signalling premature optimisation
It took a year, but that was somewhat on the side of also building an OpenAPI based Web service, the gRPC based workers. So, it wasn't just the infrastructure stuff. If I were to estimate how much time for just the infrastructure and devops tooling, then two months. It's been up and running with less than 15 minute downtime over the course of two years.

I do consider this impressive. And, to be clear, I wouldn't say this is because of a "super-developer". In fact, he had no prior k8s experience. But rather that there are thousand upon thousand of infrastructure hours devoted to the helm charts, often maintained by the people who develop the services themselves. It is almost mind boggling how much you get for almost free. Usually with very good and sensible default configurations.

In my precious work place, we had a team of 5 good engineers purely devoted to infrastructure, and I honestly believe that all five would be able to spend their time doing much more valuable things, if k8s had existed.

As for whether or not such devops solutions could be done in a day. Hm. I don't know. These things should be tailored to the problem. If you've done all of this a few times, then maybe you can adjust a bunch of charts that you are already familiar with and do what took a couple of months and impressed me, in a couple of weeks. It's a lot more than just "helm install. Done", that goes into architecting a scalable solution. Implementing monitoring, alerting and logging. Load testing stuff. Etc.

okamiueru··on Kubernetes is a red flag signalling premature optimisation
I don't think their advice about not using it in a startup is correct either. You just need to somewhat know what you're doing.

I know of such a case, where a single engineer could leverage the helm chart open source community, and set up a scalable infrastructure, with prometheus, grafana, worker nodes that can scale independently of web service, a CI/CD pipeline that can spin up complete stacks with TLS automated through nginx and cert-manager, do full integration tests, etc.

I found that to be quite impressive, for one person, one year, and would probably be completely impossible if it wasn't for k8s.

okamiueru··on Show HN: Get rid of Git submodules and never look back (now for GitHub users)
The more important downside I see is code traceability and verification. You would completely be void of both with that setup.

I'm not saying you shouldn't, as it works for you, and that's of course fine.

But, the key functionality of submodules is that the sumodule can exist on its own, as a git repo. The degree of dependency is then entirely controlled by the parent git repo.

okamiueru··on “Magic links” can end up in Bing search results, rendering them useless
I wouldn't go around saying others don't understand http. Puts you in a very awkward position when you are wrong. Which, you are. Idempotency and safety are separate concepts related to http. But, you do you. Take the advice however you want.
okamiueru··on Explaining Code Using ASCII Art
I should clarify what I mean with scaling. I was trying to describe complexity of maintaining the illustration for the complexity of what it is illustrating.

For ASCII art, this is far from linear, in most of the examples shown.

Consider some of the more complex ones shown in the linked article. The minor added complexity of adding a field, suddenly might mean you need to remake parts, or even entire visual art for it to stay congruent. You'll have software engineers hitting spacebar a few hundred times just to align things right. With proper tools, you'd just add the field, and that's it.

okamiueru··on Explaining Code Using ASCII Art
This isn't a very good solution, IMHO. Or, it doesn't scale. If you find yourself with an existing solution that doesn't scale for what you need it to, cut your losses and find a better tool or solution.

Some simple visualization using ASCII is fine. Something you can create from scratch and otherwise modify in as much time as it would take to document code. But, if you need a sequence diagram, or flow chart, what not. The tradeoff for maintenance and lack of readability makes it look silly. The "why was this developer wasting time doing things with the wrong tools"-kind of silly.

If you need complex diagrams. Create them using draw.io or plantuml, and add them to the source control. Generate images which you instead reference in the documentation in code. Tools such as Doxygen and other such tools would be able to pull in the images and actually look good. This is both maintainable, and scalable.

okamiueru··on Ask HN: Europe to East Coast, does it make sense to move at 50?
What does "love for liberty" mean to you?
okamiueru··on GitHub Copilot is generally available
Is your argument in good faith? Seems like you know enough about the matter to destinguish an API definition from implementation. That's what that ruling was about, and you seemed to know it, yet make the comparison as if it was valid.
okamiueru··on 700M users and Premium
I don't understand. I've been using telegram for some years. Could you explain how you would go about using telegram without "signing up"? And by "a number" I understand it to be an option of "not your phone number"? How does the verification go then?
okamiueru··on Tell HN: Banned from LinkedIn for Reporting Wickr Drug Spam
That's such a sad and completely avoidable situation.
okamiueru··on Despite best efforts .NET is still not an open platform
If only apple products were just expensive. For certain kinds of people, dev-tools/environment and OS are exceedingly frustrating to work with. I don't get why developers put up with it, well, other than the obvious market access.
okamiueru··on Enormous ‘rogue waves’ can appear out of nowhere
Is there a lot more to it than "random waves, it's less and less likely for them to overlap more and more, but sometimes that too happens"?
← PreviousPage 11 of 28Next →