2,283 karma · joined July 25, 2018
then they can have their own tournaments - of course, no one should actively stop them. I am more concerned that an organization managing the tournament decides to create a new category rather then putting in the effort to bring everyone to the same playing field. I mean is that not the decades long battle that made it all the way to the workplace? Should we also create female software engineering roles, and female CEO roles bc the CEO market is crowded by tech bros? If you have $1B, and you have to solve this problem, how do you split it, that's my question.
Shouldn't the work of incentivising more women be outside of the tournament and not bend the tournament altogether?
If you cannot answer, you did not author the paper, meaning you are misrepresenting your contribution, and there is already a process for this. And this is actually a really good test for any field. Use AI as much as you want, but you need to be able to explain your work. Applies to SWE as well, you need to understadn what you built, at the code level and system level.
If/when they get through this, they should start pushing for an account manager.
Their docs explain this.
I have seen this before, first hand, on lower stakes for the world, but high stakes for the org. Self imposed safety goals do not last a quarter, but the clawback is not transparent. little things start snapping back internally, new, seemingly unlrelated initiatives are funded that take resources away from this, people are let go for different reasons, until 1y later you are right back where you started. I am hopeful though, that this becomes systemic and not something any one company can easily reverse course on.
When we say the world's GDP grew by X%, what is the point of that growth? Inflation? If the economy grows as a direct effect of humanity growing, I get that. If the economy becomes more efficient and we can not get more with less, I also get that.
But what is the point of just growth, if not simply to show others that I am growing faster than you? At which point this is a meaningless number. What am I missing?
The startup however, will do the thing they advised them not to do, which is tailor their roadmap to a large customer.
But yes, this is early exit/rugpull planning. If it weren't, it would not be AI exclusive and I don't think companies are that excited to know the latest and brightest AI companies. They can simply wait for the market. But they create FOMO, and now they open a small window, make calls to know how much you'll commit and all the FOMO execs will fly in. I'll be fun.
When you record an achievement, there is no need to record another one until you surpass it. You can record attempts, but they are now just data that makes the actual record more meaningful the longer it exists without being surpassed.
Or is the underlying system still bad, as in drivers, compatibilities, audio and video codecs, networking, etc. I know on servers when some of these break they take a bit of mucking around. But it seems many companies are trying, why are they failing?
The problem comes when developers start building things without this in mind. I see simple site analytics apps in github, where the docker compose file is a web os services and the repo itself is full of init scripts and the sort. You have redis, mongo, an RDBMS container, an analytics db, kafka, all the kafka tooling like bookkeeper, then you have outsourced auth liek clerk or supabase (when the whole thing is not just some supabase chimera with edge functions and whatever else supabase is supposed to run outside your infra).
And the repo description is: simple, anonymous wesbite analytics. The entire thing is more complex than the thin you want to do analytics for. So you bring that into a cloud, and instead of a container, you are now advised, but both AWS and your HN peers that you need to replace each component with it's cloud version, such as elasticache, AKS, cognito, firebase, whatever.
All of these services as you set up, trap you into overprovisioning. Your DB needs to have 3 replicas or you have no guarantees, your auth needs an entire instance of something running somewhere or unicorns start dying.
By the time you come out for sunlight your bill could pay your rent. So you don't self host, you signup for google analytics.
Everytime I find a project on GitHub, the first thing that makes me close it immediately is whether it has a docker-compose.yaml and if it's a single, sane/dumb, low footprint deployment or a chimera.
So self hosting is alive and well, whether your app is easy to self host, and whether you know how to use just what you need from cloud vendors are different questions.