Hacker Newsnew | past | comments | ask | show | jobs | submit | ublaze's commentslogin

ICF: Inertial Confinement Fusion

MCF: Magnetic Confinement Fusion

CFS is Commonwealth Fusion Systems - https://cfs.energy/

Q is the ratio between energy in and out in a fusion system. Q > 1 is the holy grail, which implies we have more energy out of the fusion system than in. CFS is aiming for Q 11 in its prototype reactor.

SPARC is the "Smallest Possible" ARC I believe. It's their prototype reactor that they're working on that uses magnetic fields through superconductors to contain Hydrogen as it heats up into plasma and goes through the fusion process.

ARC is the 400MW reactor that will be produced (aimed for within a decade) if SPARC succeeds - it's the scaled-out version of SPARC.

It has an impressive set of people working on it (ex-SpaceX).

And yes, ARC is named after the Iron Man reactor.


Tech blog: https://www.softwareatscale.dev/

Substack to keep it simple. But I'm not extremely happy with the design.


These are company reported base salaries for OpenAI members of technical staff. The base salaries look very similar to standard tech bands.

They could be underpaying immigrants, but that's unlikely, given that it's illegal and they have a lot of attention on them.


The site has h1b in the URL. So it surely is about pay in country. Out of country its Groucho Marx territory (inside of a dog, it's too dark to see)

The site does not report on the C-suites, and I suggest on the next tier down. I wish that those people were more transparent about their renumeration but historically its been veiled. Once your pay is a matter for the board, it may or may not be available depending on the nature of the company. Privately owned I don't think have obligations to report renumeration.


That's too expensive. I'd prefer a monthly/yearly fee.


Hmm, we have tiers that reduce the % once your AUM grows. How much monthly fee would you pay btw?


Would rather invest in US Indices for nominal fees that are less than .1%. 1% is a very high fee that reduces the hassle of opening a Zerodha NRO account. 1% is 4 times the fee of Wealthfront, the company you are trying to replicate.


This is also a more efficient way of investing, which leads to higher returns because of low tracking errors. The fee more than covers for itself with the return delta you get here, refer the comment on investing in India ETF vs investing here.


Thank you!


Yeah, large-scale systems are often boring in my experience, because the scale limits what features you can add to make things better. Each and every decision has to take scale into account, and it's tricky to try experimenting.

I think it has to do with the kind of engineer you are. Some engineers love iterating and improving such systems to be more efficient, more scalable, etc. But it can be limiting due to the slower release cycles, hyper focus on availability, and other necessary constraints.


I don't think they are boring, but very important on the kind of engineer you are. At AWS I try to encourage people who like the problem space and at the very least appreciate it, but can totally understand that you don't want to do your entire career on it. Many of our younger folks have never felt the speed and joy you can get with hammering out a simple app (web, python, ML) that doesn't have to work at scale.


Does anyone know which tool can be used to make such visualizations?


Inkscape (free, Linux mainly), Gravit Designer (cloud app, happy user), LucidChart (cloud app, great IMO but disclosure: ex employee), Visio (Windows), OmniGraffle (Mac), Illustrator ($$ but excellent).


Graphviz (dot diagram notation) or Mermaid diagram editor. Emacs has good support for rendering dot notation.


I remember we migrated 2+ million LoC to being formatted by Black at Dropbox.

Our Livegrep instance with a custom Git blame implementation always crashed at the commit made to do the migration :-) We had to pause our merge queue because we didn't want to run into conflicts, and I remember the `git push` ended up taking a while.

There was only one change that we had to make to Black to get it working on our codebase - https://github.com/psf/black/commit/024c9cab55da7bd3236fd887...

Glad to see it's now stable.


When I switched the company to Black, I reformatted the whole repository history with it. Every developer had to clone the repository again and reapply their local changes to it, but in the end it was a good choice because "blame" still works perfectly since we don't have one big reformatting commit.


An alternative is to use Git's blame.ignoreRevsFile[1] option to ignore specific commits when calculating blames. The downside is that although you can save the list of commits in the repo, you cannot do the same for the config setting itself, so it calls for some light automation at scale.

[1]: https://git-scm.com/docs/git-blame#Documentation/git-blame.t...



looks like a `break` is missing after `has_special_comment` becomes True


`another_really_really_long_element_with_a_unnecessarily_long_name_to_describe_what_it_does_enterprise_style` hahahahaha, I love that test case.


To clarify, the slow git push was likely custom pre-receive hooks being slow.


I interviewed one of the creators of the Git sparse index a while back: https://www.softwareatscale.dev/p/software-at-scale-32-derri... which had some interesting tidbits.


I've been following PlanetScale for a few years and interviewed their CTO Sugu last week: https://www.softwareatscale.dev/p/software-at-scale-29-sugu-..., if anyone's interested to hear their story of building Vitess for YouTube and some details on PlanetScale behind the scenes.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: