HN user

haggy

390 karma
Posts8
Comments151
View on HN

First, congrats on getting healthy!

Secondly, since you're presenting this as a portfolio entry, I have some open, honest feedback. I quickly reviewed the repository and there are some pretty major orange-red flags that would dissuade employers from reaching out. Some of them include:

- Lack of coherent repository structure. All files under src/ with no sense of modularity

- The commit messages are very poor. Messages like "cool" and "jump jump" and "perf" do not provide any context to anyone outside of yourself (and probably not even you will remember what those changes were days/weeks from now)

- There are magic numbers everywhere. The biggest offender I found was in shaders.ts

There are more but those are the top ones I saw from my quick review. Again this isn't meant to discourage you. I wanted to provide the feedback to help you be more successful with potential employers. Cheers!

This ^^^ My answer to this question would have been a VERY weak "Yes" before the Twitter disaster. Now that we're seeing the true Elon alongside real engineer feedback, it's a HARD no.

That totally makes sense. I think you'd have a miserable time supporting this at scale if a re-compile is needed every time a new workload requires a tweaked setting or two. Config based static allocation is the best of both worlds.

I disagree in this case. Normally I'd fully agree with you but I think this animation style works really well given their use-case.

This is not really surprising considering that it's basically a (very cool) marketing article for their equipment.

Per the article: "(Currently it’s determined even before startup, at compile-time, but startup is the important point since that is the first time that memory can be allocated.)"

Sooo are we sure you can even change this via proc restart? This is saying the limits are built-in during compile...

Not a fan of what feels like an advertisement hijacking the OPs post. Most would probably prefer you just make a separate HN post.

The article body and headline are (of course) at odds IMO. The headline is very much "doomscroll" material while the article points out that interference could basically manifest as having to rely on secondary systems and protocols to land. If I'm missing something then happy to be corrected :D

A high rating is not enough to guarantee a high auction price - although it helps. Another copy of Super Mario 64 in the same auction with a 9.6 A++ rating sold for a comparatively affordable $13,200

This seems to reinforce some kind of laundering/tax evasion scenario. There is little logical reason for one cartridge to go for $13K and another to go for $1.5mm when both are certified excellent condition. It appears that the one going for far more is a product of timing. Someone needed to move a large chunk of money quickly and decided on the Mario cartridge.

Zero Data App 5 years ago

What useful software exists which works on no data at all? Even a calculator requires data

Can you point me at documentation for the fault tolerance of the system? A huge issue for streaming systems (and largely unsolved AFAIK) is being able to guarantee that counts aren't duplicated when things fail. How does Materialize handle the relevant failure scenarios in order to prevent inaccurate counts/sums/etc?

I don't know your background but the way you respond makes me think you have not been responsible for systems that multiple tenants rely on for varying workloads.

These assumptions you're making are dangerous because the variety of workloads across tenants is extreme. If you're going to do something like "kill compute no matter what" then you better have a good reason for it.