> When I need to open an editor QUICKLY.
I solved this need long ago with BBEdit (hi Rich!): I leave it running all the time. It is the only application that starts with my user login, and it is always available.
369 karma · joined December 16, 2019
I solved this need long ago with BBEdit (hi Rich!): I leave it running all the time. It is the only application that starts with my user login, and it is always available.
Those early years certainly felt painful but in retrospect provided valuable concrete experience in negotiating, marketing, and self-assessment. I learned how to figure out what others really wanted, how much they should be willing to pay to achieve their goals, and (probably most importantly) whether or not I could deliver. That period of time, when computers were exploding into small businesses, was a little magical when it came to freelance programming.
Now, ~40 years later, I find myself applying those learned skills at my current job every day. I got lucky.
My apologies if I misunderstood your question and blathered on about something else.
The only non-computer job I've ever had was my first, a six-week stint at a Burger King, and I was desperate to never do that again. I undersold my skills often, and got in over my head just as often.
It was a great, if sometimes painful, learning experience.
That sounds a bit like Semantic Satiation, where words (usually when repeated) suddenly stop making sense. I have no actual information about that; your description simply reminded me of it.
Discovering I had aphantasia so late in life -- I'm 56 -- just reinforced the knowledge that everyone is wired differently and therefore approaches Life from different directions. I knew that, intellectually, but it was still kind of a slap in the face. [2]
[2] No reason for the footnote. I'm just trying to fit in around here. Maybe if I had multiple footnotes it would make more sense....
I received full dental replacement implants (the all-on-four style) a couple of years ago. During the procedure, I came out of it enough to remember trying to get "something" out of my mouth that was bothering me, and a nurse literally shouting at me to stop.
My wife was waiting for me and could see down the hallway where my room was. She said that at one point the doctor came out of my room gagging and holding his throat. After a few minutes, he went back in.
Later, we discovered that I fought everyone in the room. I had punched the doctor in the throat, tried to rip my IVs out, etc. The incident I remember (the yelling) was just a part of it all.
I've since read up on anesthesia and the subject is both fascinating and scary ("science with a lot of art mixed in").
I showed my wife the picture and she couldn't see either woman until I pointed out features. Interesting!
This happens to me often.
* PKCE is required for all OAuth clients using the authorization code flow
* Redirect URIs must be compared using exact string matching
* The Implicit grant (response_type=token) is omitted from this specification
* The Resource Owner Password Credentials grant is omitted from this specification
* Bearer token usage omits the use of bearer tokens in the query string of URIs
* Refresh tokens for public clients must either be sender-constrained or one-time use
GM has announced that they're moving away from fossil fuels, not that they were going all-electric. Granted, electric is most feasible, but they could also be hedging their bets with alternate sources like hydrogen.
Imagine my surprise -- because I didn't fully consider these actions -- when my terminal session started ignoring my commands partway through that process. It turns out that it is a Bad Idea to delete your shell binary when you're using it.
Fortunately, VS Code's terminal uses a different shell binary so I was able to complete the upgrade there.
Another day, another reminder to Be More Careful.
Larry Niven - The Jigsaw Man
Larry Niven - The Fourth Profession
Issac Asimov - The Last Question
Which is ... correct.
I'd like to know more about the algorithm behind this.
The presumption here is that I've already thought about how long the task will take and what I'll need to complete it, plus I'm aware of what else is going on and taken that into account, so I have no real excuse for not doing the task right when the reminder pops up.
It's a bit of moderated procrastination, but it works for me.
I should note that phishing tests are just one component of many company-wide education programs regarding physical, computer, data, and network security. My company deals with very sensitive data, so information security is a Big Deal.
The problem with targeting these tests is that new employees are constantly coming in and need to be educated/trained. Also, the persistent failures do not seem to be confined to only certain work groups; they're spread around the company fairly randomly, and they move.
Exactly how phishing tests are run probably depends quite a bit on what kind of company you have and what kind of employees work there. A workforce full of programmers would -- I would hope! -- be much less susceptible to phishing scams. The sales force, possibly more susceptible. That may be stereotyping, though.
The phishing emails are sometimes very good. They appear to be from senior management and address projects or other internal events everyone knows about. Some emails are very easy to spot, in the Nigerian prince category. It is very interesting that we have that 7% failure rate no matter how good or bad the phishing email is.
In general, I think internal phishing tests are a great way to educate the workforce.