OmarIsmail

This article is amazing. I think any engineer outside of programming language builders would get something incredibly useful for it.

Not enough engineers engage with the concept of code and programming and as an industry we suffer for it. The beginning of this post does a phenomenal job of simplifying very basic but high level concepts as “what is a function” “what is a tag”.

99% or programmers don’t think about these things like this, and so get confused when these building blocks are manipulated and presented in seemingly strange ways like React components or server components or whatever. By breaking down these concepts (functions, blueprints) and having rebuilding them with simple definitions it allows the reader to start their mental model fresh and go from there.

This is a masterclass in technical communication.

Who gives a shit if it’s long. In fact I’m glad it’s long because every sentence is gold. These are deep subjects and foundational to programming and so ya, talking about them like this can take a few words.

99% of people who take the time to really read and process this post will come away as noticeably improved developers. That kind of bang for the buck is rare!

On a relative and even absolute basis the wealthy will lose substantially more money.

On a personal quality of life basis the middle class will get hit the hardest. It will impact retirement timelines, vacations, home renovations, car purchases, etc. seeing their 401k go down will make them feel poorer and want to save more and thus reduce their discretionary spending and reducing the amount of fun and entertainment they enjoy.

This is me. And fingers crossed it’ll be an uneventful few days for us both :)

You can make an exception for the pager duty providers number. That will it will always make a sound no matter what.

Mighty as an idea was cool and interesting and I hope the tech survives and continues to be developed. Fat clients have their place in the world but a solution like Mighty allows for a lot of the benefits of a fat client without a lot of the downsides.

I think this is a really interesting decision from Suhail and one not taken lightly. I think this decision is another data point that AI-infused applications are a potential new “tech platform” and we’re at the beginning of a new “mega cycle”. I.e. web2 2002-2010, mobile 2010-2020.

Folks shouldn’t be spending much energy on thinking about how Mighty may have gone wrong (and seriously the negative analysis is so boring and lame), and instead think about the new AI opportunity.

I'm going through this right now. At dayjob we have a lot of internal dependencies and libraries that are created sufficiently far from me that I treat them as third party and when things go wrong (which they do a lot) it's a nightmare to debug and work through. Easily half a day gone.

So for sideproject I'm going mostly bespoke and using very little 3rd party libraries. The result of that is there's sooooooo much boiler plate to write and it's very boring and it's hard to be motivated and productive to get through it. What's keeping me going is that once the boilerplate is done - it's mostly the foundational level of data queries + endpoints - then I shouldn't really have to touch that stuff again.

My conclusion is that there's no great answer.

Using lots of libraries is like riding a horse. It'll start moving right away but you don't have full control and you gotta find the right way to get it to do what you want, and may have to fight it if it really doesn't want to. Vs building most things yourself is like building a car. You don't go anywhere for a long time as you're building it, but once you've built it you can move very quickly and if anything goes wrong you can easily pop the hood and fix/change things up.

I think for long lived projects it's better to build the car, but also be disciplined in writing very good code + documentation. The initial build out sucks hard but that pain will get amortized over a very long future and ultimately be worth it.

And for absolutely required dependencies go with paid services. Specifically paid services where the company's primary focus _is_ providing that service. They are financially and existentially motivated to give good service, and are usually good about keeping backwards compatibility while usually staying on top of security/modernization upgrades without requiring work on your own end. A managed database is a good example of this kind of paid dependency.

The different module syntax is the problem. If we just had the standard import/export syntax from the beginning I think 99% of problems would be avoided.

Even that blogstatic "guide" is just one page.

It seems to me you're throwing a bunch of barely-built stuff at the wall to see what has traction to then actually build out. I don't think HN is a good way to do that. This now feels like a waste of everyone's time.

The idea is solid but as someone who is in the market for something like this, the product doesnt currently inspire confidence. Specifically, you’re a tool to create User Guides and yet you haven’t created a user guide for your own site. If you don’t have user guides for your own service that indicates a few possibilities:

- the tool is too difficult to use for even yourself to be worth it

- you don’t use your tool deeply so you don’t have intuitive understanding of what is needed to be improve

- you don’t actually take user guides seriously and think they are important for a company to provide

When looking at this kind of service I’m evaluating on two levels: my customers experience, and my authoring experience. By not having your own user guide filled out I’m unable to evaluate the end customer experience (search, navigation, etc).

I know you’re in beta, but I don’t know why you’d do a show HN without at least having your own user guide filled out. A big wasted opportunity.

Environment is one of the factors for my preference for fake meats, but the much bigger factor is the ethical one. Both at the fundamental level of “killing an animal for food is bad” and the larger “modern animal farming is monstrous and inflicts incalculable suffering”.

I still enjoy a burger and I can do that relatively guilt free. Totally worth it for me.

Also, this space is still very young so I expect it to improve dramatically over the coming years. Which is a great aspect about fake meats. They are a technology that can evolve and improve a great deal. Technological development with regular meat appears to result in worse treatment for animals, not a direction I want to support.

> Nowhere will a training set featuring pictures of naked children be legal.

Appropriately from the recent news stories, but it's easy to imagine at least portions of such pictures being available for medical diagnostic purposes. I've sent pictures of my children to my doctor, so presumably in the future it's easy to imagine sending pictures to an AI to diagnose which would require a suitably fleshed out (pardon the pun) training set.

We do a decent job of banning child pornography.

And bringing the two ideas together, is child pornography that is provably created by an AI still illegal?

That actually sounds pretty cool! If that's _not_ what Flow is, I hope somebody does roll with that idea.

The secret is that if you’re good enough pretty much any company can be what you want. Most people don’t really know what they’re doing so if you are good and just build stuff that is useful I’ve found that people don’t really get in your way.

If you try to ask for permission and write up docs, etc etc then it’s a pain, but if you just _do_ it resistance becomes a lot less.

Yes, graphql does indeed suck. Or rather it is not the best solution for all client-server communication that people treat it as, so it ends up being used in a lot of situations where it does suck.

Backend to backend communication is almost never graphql (is that changing in a big way?) which would indicate the main reason for graphql in a client-server situation is data saving but at the cost of complexity and other downsides. Almost certainly the data savings in many cases is not worth it.

Oh and then you have things like Apollo having cache bugs that result in incident level problems.

They address it here: https://github.com/coilhq/tigerbeetle/blob/main/docs/DESIGN....

What does that have to do with the valuation getting lowered?

If a person had 1000 RSUs that were on paper worth 40k, now they are worth 30k. Either way they can’t be sold right now. And I don’t understand how 30k is “worthless”

If it’s RSUs why are they worthless?

Funny enough these are the exact questions that founders need to ask themselves before committing to an idea. YC has overly broadened this to “make something people want” which at first order needs to be true. The questions you’ve laid out here are the direct implications of “make something people want”.

I've been looking for something just like this! I find that people get really weird about solar stuff, so I'll explain why I've been looking for something like this.

1. I believe that man-made climate change is real and we should do something about it.

2. I want to limit/eliminate my own family's personal contribution to the warming of the planet for ethical and emotional reasons

3. I believe that solar is a "green" way to generate electricity, and at the limit if every house and building was covered in solar panels that would be a great world to live in

4. I want to help make that world a reality, and I'm not looking to maximize my ROI on the investment, it's not just about the money

5. I'd prefer much more solar energy production even if it's not the most efficient

6. I currently only have access to install solar panels on my own roof (which I'm already doing)

7. I think non-green energy production will only get more expensive, so solar energy is a decent diversified asset in a broader investment portfolio.

I've actually gone pretty deep in thinking about how I could do this, i.e. get a bunch of investors together and install solar panels on business roofs like schools, warehouses, etc.

I'm gonna request early access to this.

If I ever look for a job again my plan is to give the hiring managers my performance reviews from my previous company. There's enough information in them that speaks to the kind of engineer I am in the real workplace working on real projects with real people. I think that + a 1-2 hour conversation to verify that I know what I'm talking about (i.e. I didn't forge the perf review) should be sufficient for hiring manager to assess if I'd be a good fit in their role. I think that will be a lot better/easier for everyone.

Are there natural “fault” lines for Russia to split into?

If he drops a nuke on Kyiv I honestly don’t know how the world will or even “should” respond.

It really goes to show that nukes just shouldn’t exist- there’s no “counter” to them if the other side is suicidal

The industry does not properly reward long tenure. If the person stays curious and hungry then the accumulated knowledge and experience they hold is worth a tremendous amount. Smart companies will start appreciating and compensating for this in the future.

For now.

But now that the pool of people that could work from the jungles of Brazil has increased 10-100x there’s a lot more incentive to making that possible.

These articles are so good. Very informative for a product engineer such as myself. Allows me to create a much clearer and more expansive mental model of the running systems.

This article does a very good job of explaining the main difference between column vs row databases at the storage level. Knowing this low level structure is extremely helpful to make considered trade offs when choosing the right technology.

This is worth a read.

At this point I literally only play games on Xbox Game Pass and I'm playing more now than ever before. It's truly unreal how good of a value Game Pass is.

I take this _very_ seriously but didn't have a name for it until now.

I totally agree that many/most software organizations don't take it seriously. But I don't think that it's because of a lack of desire, I think it's a lack of even knowing it's a thing.

I put my skills in writing clean code in my most recent performance review but I didn't do a good job of describing it. It's also not something that is apparent to higher ups, but is readily apparent to colleagues who describe the code as a "joy" to work with.

I think we need to get better as an industry at measuring "Code UX" in a quantified way, and then that can start to be a meaningful area of progress that engineers can use in their career, which will motivate them to improve on that metric.

"Almost none"? https://trudeaumetre.polimeter.org/

143 out of 230 kept with 20 out of 230 in progress.

Political discourse can be difficult enough without hyperbole making things worse.