7,589 karma · joined May 29, 2014
https://stackoverflow.com/questions/6067227/what-is-a-good-w...
https://stackoverflow.com/questions/8968434/i-am-having-trou...
https://stackoverflow.com/questions/20154313/how-can-i-gener...
As someone who was a budding programmer, I felt like my questions were decent attempts at laying out my problem but they were closed anyways.
https://www.sfgate.com/business/article/adobe-laying-off-600...
https://www.cnet.com/tech/tech-industry/adobe-to-cut-9-perce...
https://www.cnet.com/tech/tech-industry/adobes-transition-to...
They went through a heavy period of layoffs for a few years and now are killing it and it meets your criteria of about 10 years ago
Not saying this is how I feel or act though.
I've always been on the get it done side to the chagrin of my peers but I've also never impressed anyone with what I've came up with so who knows.
My personal opinion is that if you don't get with the program, you're probably going to get left in the dust or going to have to split off and do your own thing where you can control what's going on but I think in general in a capitalistic society, the business just wants to get to the next thing to make more money and subpar or middling quality is good enough.
I should caveat my comment that this doesn't apply to pacemaker software and higher end software engineering
This wasn't a half assed test but a legitimate effort to improve something that we never prioritized
We had a legitimate 25% reduction in users giving up logging in in a system that has millions of users.
We ran a 50-50 AB test for several weeks to confirm the data and then turned it on completely
edit: If you haven't already read my post, I'd also like to say that the benefit AI gives us is that I worked on something I never get to work on, the analyst got to try a hunch he always had, and we got to see it go live in a day. If it didn't' work out, we were out a day of work which beats the few weeks of an effort prior to AI that we would spend on something just to find out it didn't work.
I got the opportunity to rewrite our aging login page just as a fun experiment. I sat down with one of our analysts and we just went to town in a zoom trying out stuff with claude until we made something pretty sweet. Ran it through all our systems for accessibility, performance, etc and it came out clean. Made a PR and fired up a test that day in production. I haven't written a lick of our front end framework ever in my entire life and we were able to build something that has had a marked improvement in our user engagement in a day.
You feel satiated and you're reducing your caloric intake. You can only eat so much beef jerky compared to eating a whole bag of chips before getting sick. It's helpful for people who are binge eaters.
I don't really see why everyone is up in arms about this. You are able to print in LAN mode or directly through USB drives without going through bambus servers.
Their slicer is open source but it downloads a plugin once you launch it if you choose to which is closed sourced that interacts with their APIs.
Someone reverse engineered the plug-in and put it into orca slicer and then claimed that the plugin should have been GPLed to begin with which I find dubious. I don't really see it being much different than downloading closed drivers on Ubuntu but I'm also not a open source lawyer.
To me, the problem with all of this is that it seems strange to want the plugin when bambu will just shut off their resources to unsigned versions of the network plugin if the orca slicer dev got their way.
I'm open to being convinced but I just don't think the cross-section of people who want this would actually want prints going through bambus cloud so this effort really feels vain.
It also feels like bad framing as well because every post I see about this thing really tries to blur the line and claim this plugin and orca slicer are one and the same.