I never understood whose blame the poor memory falls on? In my opinion it was on him to stay organized - something he never made an effort to do. Others would say it was on me to communicate to him what he told me. I don't get paid enough to be his executive assistant. And I don't see the point in communicating better if he would just forget again.
Other times his memory was bizzare. Like he would remember some off comment I'd made to him in a 1-on-1 and then use it as a way to butter me up or appeal to me. I once mentioned to him I follow news in the "programming space" (aka reading this website). And he seemed to remember this whenever he needed to appeal to me to look into some new platform feature clients were requesting. "You read a lot about this stuff right??? Take a look into PDF generation using this library. You read a lot about this stuff right??" I think he thought he was juicing up my ego with this. So bizzare.
Of course its the same manager who did the fundamental sin of complaining downwards to me, and about my peers whenever one of them messed up. Dude you're the CTO. If you can't maintain face then I will lose all confidence in your ability.
OK I'm going to stop venting about my last boss now. Sorry!
https://www.ifixit.com/Document/CPMKU1yOZAYVXbpB/FixHub_Sold...
What he says matches their documentation as well:
>Blue LED: The iron is below 40° C / 100° F and is safe to touch.
>Purple LED: The iron is actively heating up or cooling down. Iron tip is not safe to touch.
>Orange LED: The iron has reached the user-set temperature and is ready for soldering. Iron tip is not safe to touch.
> While there’s no display, the illuminated ring behind the grip does provide a visual indicator of what the iron is doing: solid blue means it has power but the heating element is off, a pulsing blue indicates the iron is heating, and orange means it has reached the desired temperature. If you flick the heater switch off, the ring pulses purple until it cools back off and returns to blue.
However, the client is going to want to know (A) how much it’s going to cost, and (B) how long it’s going to take. These are extremely reasonable questions in most cases/industries. To answer these questions with a shrug is a nonstarter. The client is working with a time budget and a financial budget, and they need to have some sense of the numbers.
If the Waterfall and Agile methods are opposite ends of a spectrum, somewhere in between is where I’ve found an acceptable middle ground for both developers and clients.
This is not correct, it pulses blue indicating the iron is heating, and when turned off, pulses purple while cooling.
Edit: as other commenters have mentioned, an on-prem version would certainly ease concerns a bit.
Few will instead read the RHEL provided documentation. Then they could maybe figure out whether there's simply a tunable (getsebool -a) which would enable the desired behavior, or if properly labeling files (semanage fcontext / restorecon) would do it, or even take the steps to add to an existing policy to allow for a specific scenario which somehow was not implemented. Even adding your own policies "from scratch" is certainly doable and provides a great safety net especially for networked applications.
Anyway... we all know disabling security or not implementing it in the first place can really save you a lot of time. At least in the short run.
The way I put it to my clients, and staff, is simply that security comes at the cost of convenience.
Just a small note, on safari mobile if I expand the Edit and then Convert sections, they open on top of each other.
Wish this could work, but my experience is that getting people to use even the first layer of threads is very difficult, especially non-technical people.
IMO most often complex discussions will devolve into a "let's just jump on a quick call to settle this", for better or worse.
The feature I am looking forward to the most in comminication apps is having a machine learning model listen to those "quick calls", generate summary and action items and post them right back in the thread. You get the benefits of both worlds that way.
Indeed. We use Google Chat which is roughly a Slack clone in terms of structure. A discussion will start at the root level, and then branch into a thread after a few comments, but some users will miss this and continue to use the root level, which of course gets mixed into unrelated comments. It’s easy to create a mess, and it’s even worse when a discussion has multiple threads.
This “thread-based” style of space/channel was forced upon Google Chat users late last year. Prior to that, we had the option of “topic-based” channels, where every discussion had its own thread and there was no root level. Any reply to a topic would bump the topic into view. These were great for some use cases (one topic for each software issue, one topic for each support case, etc), and were easy to understand for non-technical people, because you could explain it like “each topic is like an email chain”. We got into the habit of summarizing the first comment of each topic, which always remained visible, so you could browse the list of discussions, again, much like email.
Anything that you can relate to email is great for the non-tech crowd.
I don’t know much about Heroku, or if it’s been enshittified (yet?), but a company that offers a free product and somewhere down the line starts charging for it sounds fine to me.
And anyone who believed a product produced by real people working at a real company could be free forever was kidding themselves.
(In general though I agree with the sentiment of the article.)