Interesting. I saw the Qidi X-Plus 3 advertises 600mm/s vs Bambu P1S 500mm/s. And the P1S doesn’t offer a heated chamber. Have you noticed a difference in quality from the heated chamber?
I haven’t yet been convinced of the bambu cool-aid mainly because of closed software. Klipper support is a big value prop. Who knows how long bambu will support OS versions and what happens if they start charging for cloud. It’s a young company, so not a lot of confidence yet.
Looks like a sweet printer. I was thinking of buying a Bambu for the holidays, but this looks like a better deal.
What 3D printer do you have? The print looks good.
Isn’t OpenAI also naming their next model Q as well (Q*)? Or is this the same model and OpenAI is licensing to Amazon?
Sounds like you are a real pleasant person to work with
I appreciate your opinion. I know that the qualification I made is a controversial one as everyone wants to be an ‘engineer’, but I’m still confident it holds. Applying physics is not purely at the atomic level. In web development, one of the physical challenges can be bandwidth, however, while most people claim to concerned about bandwidth, in reality they don’t do anything about it. Minifying code is cool, but that’s not doing any engineering by itself. Calculating the throughput your datacenter can dish out for your 1million users as you write a function that optimizes load vs lag of streaming video, that’s engineering.
Thinking about user interaction and experience is more psychological than it is physical in most cases. Designing the user experience of a medical device or cockpit switch are both not automatically qualified for engineering: unless, you are designing the medical interface to overcome spasms that someone with Parkinson’s has, or, the cockpit switch is designed with a plastic mix to survive the temperature, vibration or weight requirement, it’s going to be more of an art-than-science. I’m not saying one is worse, but we need to make the distinction between designers, developers, scientists and engineers.
I understand that everyone wants to be an engineer, whether for pride or just to feel more important (hell I want the engineer title too). Unfortunately, the tech industry (with arguably one of the most conflated egos) liberally tossed around software engineering to every role to attract talent and I don’t see that changing. It’s a profession, so whatever you are being paid to do will determine if you are engineering
I typically tell people that engineering is applying physics. If you aren’t directly interacting with the physical world, you are most likely a developer.
Working on an app, no matter how complex (or unessarily convoluted) generally makes you a developer. If you aren’t thinking about impact of clock cycles, actuation/hardware interfaces or sensing, there is a high chance that the work you do has little to no risk or a chance of failure that is governed by the physical world. As said in other comments, engineers design and sign off on things. There is an implication that there is an unknown constraint, unlike a fully observable software environment.
I think if you have the goop, then you can add filler ingredients to sell at a lower cost. So one carrot may make two 50% concentrate carrots with some harmless filler ingredients.
If you look up Zied Aouina (issue creator), he’s a principal SWE at MS. Seems within his power to read the codebase and figure out his question if he claims he can’t find the documentation.