Readit NewsOr that reaction is really "that looked simple, easy and like the last 10 "elegant solutions" that caused fires".
"I made this x times better" is not relevant to _most peoples in any org_.
That's the dark secret. Nobody cares how good of an engineer you are _unless there is a fire to put out_. After which you get pat on the back and back to usual business.
There are situations where years of impeccable, high value diligent work is rewarded.
But what is more common is that the rewards go to those who are in politically expedient position to get the rewards. Favourites, culturally aligned folk, etc. And sometimes it's not even about you or your boss, but the politics in the organization at large. "You are not allowed to promote anyone due to budget" is a very common thing.
So I guess what I mean to say is if as an egineer you want to retain your sanity, when at work focus on maximizing business value. If you know a kick-ass solution that is 10000x better than industry standard go with it but know this - nobody will care! Nobody believes _someone in their org_ could have beaten _industry standard_ unless the org is very unique. What you get is small increase in your reputation - and sadly nobody recognizes how hard that was. Maybe you will meet some other engineer at some point who has tackled that same issue - and then you can bond over the solution.
A large part of software ecosystems is about business, politics, and the large scale impact of technology.
Saying this as an IC whose previous tasks at previous employer could have employed _teams_ but since we were allowed to deal with them smartly it was just me.
So if you know a 10000x solution to a problem many people have - that's a good opportunity to consider can it be productized!
And on the other hand, the complexifier (you know the type) ships rude goldberg gizmos just waiting to go off-kilter - and then they come in and save the day - and get rewarded. This creates a very strong "emperor has no clothes" syndrome until reality hits the organization really hard in the face. More often than not these horrible solutions are "good enough" and the show just goes on.
Don't take it too seriously! That's what people are like!
1. Optimize things so that they work 10 000 times faster because it makes us look incompetent (must be done slowly to show gradual progress).
2. Brag about such optimization (to stakeholders) without first synchronizing this with them (so they can brag proportionally to their pay rate :) ).
"I made this x times better" is not relevant to _most peoples in any org_.
That's the dark secret. Nobody cares how good of an engineer you are _unless there is a fire to put out_. After which you get pat on the back and back to usual business.
There are situations where years of impeccable, high value diligent work is rewarded.
But what is more common is that the rewards go to those who are in politically expedient position to get the rewards. Favourites, culturally aligned folk, etc. And sometimes it's not even about you or your boss, but the politics in the organization at large. "You are not allowed to promote anyone due to budget" is a very common thing.
So I guess what I mean to say is if as an egineer you want to retain your sanity, when at work focus on maximizing business value. If you know a kick-ass solution that is 10000x better than industry standard go with it but know this - nobody will care! Nobody believes _someone in their org_ could have beaten _industry standard_ unless the org is very unique. What you get is small increase in your reputation - and sadly nobody recognizes how hard that was. Maybe you will meet some other engineer at some point who has tackled that same issue - and then you can bond over the solution.
A large part of software ecosystems is about business, politics, and the large scale impact of technology.
Saying this as an IC whose previous tasks at previous employer could have employed _teams_ but since we were allowed to deal with them smartly it was just me.
So if you know a 10000x solution to a problem many people have - that's a good opportunity to consider can it be productized!
Yes we are now dealing with an automated Photoshop. And somehow the people in charge have decided to do something about it, probably more for political or maybe darker reasons.
So let me make a suggestion: maybe France or the EU should ban its citizen from investing in the upcoming SpaceX/xAI IPO, and also Microsoft, NVIDIA, OpenAI, Google, Meta, Adobe, etc. ?
Hit them hard at the money level... it wouldn't be more authoritarian than something like ChatControl or restricting access to VPNs.
And actually all the mechanisms are already in place to implement something like that.
I'm sorry, but I don't understand any of the arguments above.
If we presume a dark control motivation then having shares in the entities you want to control is the best form of control there is.
I find this to be the most obvious game plan here. Makes total sense from financial engineering point of view.
You _might_ get to develop nice tech/IP to enable other space based businesses at the same time. "we sold them on X but delivered Y". So it's a bit of a hail mary, but makes total sense to me if you want to have a large budget for inventing the future.
Once you can demonstrate even a fraction of this capability of operations ... I think you can sell a "space dominance" offering to Pentagon for example and just keep pedaling.
"We are going to build the perfect weapon" does not necessarily entice as large engineer population as "we are going to Star Trek".
Another thing - if Moon is going to be a thing, then _properties on Moon_ are going to be a thing.
In theories of value in post-ai societies scarce assets like land are going to become more valuable. So it's a long term plan that makes sense if you believe Moon will be a realestate market.
The compact answer is software complexity, intrinsically complex algorithms and geometric robustness. Data model may be difficult depending what you want to do. Robust import. Robust export domain to domain.
The last two are especially nasty if you are solo since there are no good specs here. There are _specs_ but what happens in practice is that each party has their own implementation that almost works, except in n. corner cases. Then you need to figure out is your software wrong, or is the input data wrong, and not rush to hasty conclusions. This will be time consuming.
This is why I try to encourage new Linux users away from Ubuntu: it's a laggard with, often important, functionality. It is now an enterprise OS (where durability is more important than functionality), it's not really suitable for a power user (like someone who would use Zed).
You really want enterprise standards support for your graphics API.
Bleeding edge ...is not nice in graphics. Especially the more complex the systems get, so do the edge cases.
I mean in general. If you are writing a high end game engine don't listen to me, you know better. But if you are a mid-tier graphics wonk like myself 20 year old concepts are usually quite pareto-optimal for _lots_ of stuff and should be robustly covered by most apis.
If I could give one advice for myself 20 years ago.
For anything practical - focus on the platform native graphics API. Windows - DirectX. Mac - OpenGL (20 years ago! Predates metal!. Today ofc would be metal).
I don't think that advice would be much different today (apart from Metal) IF you don't know what to do and just want to start on doing graphics. For senior peeps who know the field do whatever rights for you of course.
Linux - good luck. Find the API that has best support for your card & driver combo - meaning likely the most stabilized with most users.