HNHacker News
TopNewBestAskShowJobs

0x500x79

459 karma · joined July 1, 2020

submissionscomments
0x500x79··on De-cloud and de-k8s – bringing our apps back home
I know you are sharing your experience, others are as well. Let's not dismiss other's experience just because it doesn't match our own, the truth is most likely somewhere in the middle. Especially when so many people are clamoring saying that they had pain using K8s.

The initial deployment for EKS requires multiple plugins to get to something that is "functional" for most production workloads. K8s fails in spectacular ways (even using Argo, worse using Argo TBH) that require manual intervention. Local disk support for certain types of workloads is severely depressing. Helm is terrible (templating Yaml... 'nuff said). Security groups, IAM roles, and other cloud provider functions require deep knowledge of K8s and the cloud provider. Autoscaling using Karpenter is difficult to debug. Karpenter doesn't gracefully handle spot instance cost.

I could go on, but these are the things you will experience in the first couple days of attempting to use k8s. Overall, if you have deep knowledge of K8s, go for it, but It is not the end-all solution to Infra/container orchestration in my mind.

I fought with a workload for over a day with our K8s experts, it took me an hour to deploy it to an EC2 ASG for a temporary release while moving it back to K8s later. K8s IS difficult, and saying it's not has a lot of people questioning the space.

The way I see it is it starts off easy, and quickly ramps up to extremely complex. This should not be the case.

I worked at a company that had their own deployment infra stack and it was 1000x better than K8s. This is going to be the next step in the K8s space I believe and it may use K8s underneath the covers, but the level of abstraction for K8s is all wrong IMO and it is trying to do too much.

0x500x79··on De-cloud and de-k8s – bringing our apps back home
There are also discussions around CapEX versus OpEx that apply here, and depreciating costs over time. There is a trade-off of agility, cost, and maintenance, but the markup on cloud is quite high.
0x500x79··on De-cloud and de-k8s – bringing our apps back home
Hey Melingo, I noticed that you responded to a lot of different threads in this post. It seems like you are a bit dismissive of people's experiences using K8s. I have also run K8s at scale, and it is not easy, it is not out of the box in cloud providers. There are a ton of addons, knobs, and work that has to be doen to build a sustainable and "production ready" version of K8s (for my requirements) in AWS.

K8s is NOT easy, and I do not believe that in it's current form it is the pinnacle of deployment/orchestration technologies. I am waiting for what is next, because the pain that I have personally experienced around K8s that I know others are feeling as well does not make it a perfect solution for everything, and definitely not usable for others.

At the end of the day it's a tool, and it is sometimes difficult to work with.

0x500x79··on Elon Musk reportedly had his own tweets prioritized out of jealousy
I have noticed a large difference in the past couple of days in my timeline. Every time I load the page there are 4 Elon tweets in the top 100 (with Elon being the top entry every single time). There are also an increasing number of ads in my timeline, every 4-5 tweets has an ad.

I finally had to mute Elon with the terrible memes and too many tweets in the feed. I could have sworn I did this a couple of months ago, so I'm surprised I had to do it again.

His tweet around "absolute block versus percent block" made sense to me, but even so every single time I load twitter his tweets are at the top of my page, it's too much and I wouldn't be surprised if he does have a factor enabled due the changes I have seen recently.

0x500x79··on How did NPR’s pre-election poll get things so so so wrong?
It was the outcome... on a much, much smaller margin that usually happens around this time in the cycle.
0x500x79··on The Sam Bankman-Fried empire crumbled. What happened?
I love the veritasium video on luck. I highly recommend anyone who is interested in this concept watch it.
0x500x79··on How did NPR’s pre-election poll get things so so so wrong?
I think that is the point: Polling/Outlets had them getting a massive lead, keep in mind too that this was the worst performance for midterms for the party that does not hold the presidency in a very long time. Usually the party that has the presidency takes a larger share of the house in midterms. The fact that the polling was calling for a "Red Wave" and that the "Red Wave" severely underperformed is the thing that is being investigated now.
0x500x79··on Serving Netflix Video Traffic at 800Gb/s and Beyond [pdf]
Awesome feats of engineering here taking hardware and software into account when designing the system for a holistic approach to serving content as quickly as possible!

The slide deck background though: At least half of the products in the slide deck template are no longer on Netflix...

0x500x79··on Pearson Says Blockchain Could Make It Money Every Time E-Books Change Hands
In my comment history I stated that in a lot of ways NFTs feel like they were moving towards the old-school DRM. It appears others have caught onto this -- I don't like this movement.
0x500x79··on EA: The Human Story (2004)
I see that "Vote with your feet" got downvoted in the thread, but it's true. I worked for another one of the large game studios in the US for a long time. The practices employed at the game studio were built around keeping people attached to their jobs because they love video games and loved the games we built. It was weaponized excessively.

Almost every town-hall, all-hands, etc was framed around the product and keeping players happy (we need to deliver this by this date so you have to crunch). The hiring pool was primarily people that played the games we developed and there was some psychological warefare going on that attempted to prevent attrition based on building what you loved.

The quote from the article is: > No one works in the game industry unless they love what they do.

This is pretty true and can be very toxic in your "job". My advice: Don't love what you do for work THAT much. Keep a bit of a disconnect and live your life still. In the modern tech industry you can leave, you can find a job that treats you well, don't make your identity a "video game developer on X game" because that is a recipe for burnout.

The issues that stemmed from this are impossible to outline. People made subpar decisions, dealt with inhumane conditions and harassment, took lower pay, and at the end of the day has caused REAL harm in the industry (suicides, trauma, etc). We need to be better and hold these companies accountable from every aspect of not buying games, not working there, and attempt to make the industry better.

I left my stint at video games and went to a different company. The pay is better, the working conditions are better, my thoughts are not stifled because of internal politics.

The industry has changed quite a bit since 2004. During that time publishers were key and many times deadlines were set by the next "drop" for the publisher, but many of the problems with the industry have stayed around and video games are not worth it.

0x500x79··on Melvin Capital, hedge fund torpedoed by the GameStop frenzy, is shutting down
I am interested to see what they tackle with NFTs. I have heard a lot of suggestions, and there might be a place where blockchain technologies could service the world with them but I am quite bear-ish on NFTs.

Running a game rental service/resell service could be a good use of that technology if they needed ultimate transparency/auditing of records.

0x500x79··on Tesla FSD Beta almost causes a head-on collision [video]
The original post is "fine", although a bit antagonistic. The point still stands though.

I do not think that this feature should be on the road and it's not "that the car is drunk" it's that the Autopilot feature is fundamentally is mis-designed. Take a look at any thread related to Tesla Autopilot and you have experts calling out that the lack of Radar/Lidar is absolutely reckless. This is a clear reason why: the cameras ability to discern objects is limited and can cause erratic behavior under normal circumstances.

The cost/part cutting option of removing these sensors (or not using them) has time and time again shown that it can act erratically. I don't want to have drunk drivers on the road and I don't want this Autopilot on the road. Both are bad options, but the way that this is marketed to the every-day person makes it seem like it is ready to ship and you can "be drunk and Autopilot will take the wheel". We are quite far from that. FSD needs to exceed the capabilities of a human or prove that it has dramatically less deaths/accidents per mile than human drivers.

I work in software, I work with ML algorithms. I don't trust either with mine or my families life right now. I know that there are life-critical software deployments, but who is regulating Tesla Autopilot right now and are they doing enough? The NTSB is trying... we will see how it works out.

0x500x79··on Tesla FSD Beta almost causes a head-on collision [video]
The trick is its "Fully Self-Driving" TM. Which doesn't mean what the rest of the industry means by that.
0x500x79··on Tesla FSD Beta almost causes a head-on collision [video]
I got curious. There is a tiny bit of rain in the video but according to tesla that should be supported:

"Many factors can impact the performance of Autopilot, causing the system to be unable to function as intended. These include, but are not limited to: poor visibility (due to heavy rain, snow, fog, etc.)"

But then it goes on to say: "right light (due to oncoming headlights, direct sunlight, etc.), mud, ice, snow, interference or obstruction by objects mounted onto the vehicle (such as a bike rack), obstruction caused by applying excessive paint or adhesive products (such as wraps, stickers, rubber coating, etc.) onto the vehicle; narrow, high curvature or winding roads, a damaged or misaligned bumper and extremely hot or cold temperatures."

What? This is an amazing set of limitations that are normal occurrences on the roads I drive every day. These do not seem like edge cases.

I hate the marketing from Tesla on this feature. When it is mentioned in press it makes it sound like the self-driving/autopilot is nearly done when in fact there is a ton of work that needs to be done here and a lot of people question whether their current approach can even work. I am by no means a self-driving expert, but this terrifies me.

From the results in the video it is dangerous to have this on the road. I do not want my family anywhere near a car that is operating in autopilot mode.

0x500x79··on Vuls: Agent-less vulnerability scanner for Linux, FreeBSD
I personally really enjoy using Trivy. It has quite the coverage and the CLI is great. They keep adding more and more functionality and it is open source.
0x500x79··on Apple employees criticize work-from-home policy in open letter
I think that a lot of those things can be replaced with new techniques as time goes on. Just because this is how we did things yesterday doesn't mean there aren't better ways to do this it just requires some thinking and investment, IMO.

The tooling that has been developed during the pandemic has taken this space forward by leaps and bounds and I expect this to continue.

Instead of focusing on the how, I would focus on the outcomes you are looking for and lets investigate paths forward for those outcomes.

My two cents: There is still body language over video calls, Miro and other whiteboarding solutions work pretty well, not every day needs intense whiteboarding sessions so have onsites when those are required, and good riddance to the lunches with colleagues. If we wanna have lunch let's get on a call and/or have some one-on-one time setup instead of thinking that lunch is somehow a team building exercise.

Not to mention the IMMENSE benefits you get from remote work. Having those tradeoffs and changing the way we work: I am all in.

0x500x79··on My NDA is expired. It's worse than you know, AMA
Some of these types of things happen at other gaming companies as well. I worked at a leading multiplayer online gaming company that has some of the most played games in the world.

There was a person that pushed for a feature in a game citing "decline in player base" that needed to be remediated ASAP. The data was being shown with reports that this was the case and these reports were escalated to the CEO and leadership for the game.

The feature was in development for over a year, released, and had incredibly negative player reception. So much that we started to see an ACTUAL decline in player engagement due to the nature of the change.

Retrospectively, re-analyzing the reports we found that there was a critical transformation happening that caused for most of our players and our most engaged players to be removed from the number of total players. This was an incredibly small bug that was caused by not accounting for a previous feature release in the game.

Essentially a data engineering/PM bug and pushing of a perspective caused for a lack of double checking the data and caused for the company to make an incredibly bad bet on a new feature that actually removed player engagement.

This is why it is helpful to use data, but validate, and listen to players at every step of the way. Player happiness will drive engagement, manufacturing engagement is much harder.

0x500x79··on GraalVM 22.1: Developer experience improvements, Apple Silicon builds, and more
I haven't touched this in a long-while, but I believe startup will be impacted but post startup the impact should be smaller once the binary has been loaded. It depends on how your executable is used of course, but a hello world application will show the worst performance degredation since the code is loaded then executed once.
0x500x79··on College Was the Biggest Mistake of My Life
The college system should not be destroyed but be re-thought. I think that the following conditions should be put-in-place: 1. We should stop focusing on universities for any jobs that don't require it. Open up community college degrees to be 4 year for professions that don't need university-level depth. 2. Any profession that is "civic service" should have the debts paid for by the state/federal government after X-years of service. 3. Limit the number of loans available for certain degrees.

The article talks about film degrees being not very useful long-term. This should not be something that requires taking 100k of debt out of and we should not push teenagers to take on these loans.

For civic professions like teachers, librarians, medicine (nursing): These are jobs that are required for a functioning society. We should not push 100k of debt for a 40k/yr job. Wipe out the debt after a number of years of service.

I am not at all disappointed with my decision to attend university, I make plenty of money to pay loans due to being in an affluent career (software engineering). The article calls out that STEM, Doctors, etc should have university-level education and I agree. Let's get away from having students rack up 100's of thousands of dollars on debt for degrees that don't provide that value over 10-20 years to the receiver.

0x500x79··on GraalVM 22.1: Developer experience improvements, Apple Silicon builds, and more
Have you tried taking a look at UPX for the binary size? I found that it significantly decreased the size of the binary to the point where the problem was more the size of my dependencies (large JARs that could not be optimized away) and could get the binary to a completely manageable place. They aren't C small, but they were definitely better than traditional Java apps by an order of magnitude.
0x500x79··on The bottom is dropping out of Netflix
I don't think I agree with this level of negativity around plex, radarr, and sonarr. Using a seedbox provider and all of these things are setup and don't need any additional tinkering. You are right that the indexer is probably the least friendly part, but set it up once and it keeps working for over 6 months at a time.
0x500x79··on Musk announces funding secured for Twitter buy
What about the reports that he canceled customer's orders after a blog post that they have made?
0x500x79··on Proposed bill would shorten California workweek to 32 hours
Wrong comment? The comment is saying move out of big cities. I agree.
0x500x79··on Ask HN: Have you ever switched cloud?
I had a company that wanted to move from AWS to GCP. This was a top-down decision that was made with an incompetent "tech lead" stating that we could move everything and save money with the 10 year commit hundred million dollar contract in Google.

It failed, horrendously. Even though multiple people in the organization were calling out how bad of an idea it was they still moved forward. Google has some nicities with how things connect, setup, etc, but at the end of the day they are cloud providers and not everything they provide is a silver bullet.

This project was canceled after 3 years after spending millions on migrating since the migration was not a drop-in replacement (no one thought it was except the "tech lead").

There are a lot of things besides tech that can affect these projects. If you hire AWS experts and they are having to be AWS experts expect to need to hire GCP experts.

0x500x79··on Spring Remote Code Execution Vulnerability
This is true, but seems unlikely from my analysis this far. The class loader behavior is vastly different and attempting to access classes is failing to write fields (getting the default: Field is not accessible when attempting to write bean) on all payloads that I have been trying.

I have stopped my research for now because of the limited scope so I am not spending more time debugging the exact differences in the class loaders in use here, because the configuration required for the exploit to work makes 99.9% of my use cases just plain not work as it is default web form marshalling which we do not do.

We of course are updating: You should update too, it's good hygiene, but the fact of the matter is this is no where close to the same blast radius for the reason that it requires such a bad configuration to start with and doesn't affect non-public services like log4shell had the possibility to do.

0x500x79··on Spring Remote Code Execution Vulnerability
There are spring samples that are vulnerable. There are bound to be vulnerable applications. However to equate it with log4shell is clickbait. This is no where near as bad because of the preconditions required.

At my company we are doing our due diligence as a java shop and in all the code we have been scouring we have not found anything exploitable.

The configuration in use here is not the most common for modern development practices and spring. This only affects non JSON APIs using the WebDataBinder.

The do not believe the point about tomcat is correct. Testing the most simple payload that directly interacts with the class loader is not triggering because the class loader in non-standalone tomcat does not allow accessing these fields.

In fact tomcat is patching this as well to prevent this from happening. This configuration of Tomcat is part of the problem. I'm open to seeing proof otherwise, but so far there has been nothing published that shows that other servlet configurations are exploitable.

0x500x79··on Spring Remote Code Execution Vulnerability
I have done quite a bit of research on this vulnerability in the last day and it is no where near the level of log4shell even though it keeps getting compared to it.

The problem in spring is the WebDataBinder able to manipulate objects through the class loader. This affects Java 9+ because the previous mitigation of the class loader access is insufficient with the introduction of Java modules. The exploit utilizes a path from the current class to the module to the classloader, where previous mitigations removed access to the classloader from the class directly AFAICT.

The reasoning that this isn't THAT bad: this only affects the WebDataBinder marshalling which happens for default web form POST content types. Utilizing the commonly used @RequestBody annotation (for proper marshalling from JSON/XML) is not impacted. Utilizing the @RequestBody annotation causes marshalling to use the HTTPMessageConverter which is not affected.

On top of this the deployment matters. Different servlet containers use different class loaders/expose different class loaders. Currently, I have not seen an exploit for this in embedded tomcat (my debugging of this code path will not inject in code, presumably because the URLClassLoader is different than the class loader provided in the standalone tomcat deployment). I have not investigated whether this is because of security checks or some other functionality.

So very specifically: 1. You have to be using the WebDataBinder (not default for JSON serialized endpoints) 2. The servlet container matters (embedded Tomcat) 3. The endpoints have to be known or spidered

Overall, I believe this vulnerability has been quite overhyped right now.

0x500x79··on Nintendo is removing switch emulation videos on Steam Deck from YouTube
There should be more accountability for incorrect DMCAs. I see why Nintendo is doing this, but it is wrong. Nintendo is famous for reselling old games on each and every new platform they build and this takes away that revenue.

According to a thread on Reddit this video only showed emulators and not ROMs. Pretty wild that there is no accountability for these actions.

0x500x79··on The “misinformation problem” seems like misinformation
Nothing is wrong with letting people choose, forcing incorrect information to people... that is wrong.
0x500x79··on The “misinformation problem” seems like misinformation
And factoids don't mean that there is analysis being done on those facts. I can state partial facts or misleading facts all day long that might get upvotes/retweets. That doesn't mean that it is properly conveying information that is needed to analyze the subject.

The Covid19 vaccine discussion isn't: "There are side effects that are worse than you think". There are hundreds if not thousands of data points that have to be analyzed together to understand the negatives or benefits of something as complex as this. Cherry-picking on factoid to back up your bias does not make you smart.

← PreviousPage 3 of 5Next →