for me the journey is the things i can do through creating various things in various contexts and authoring the code itself is a small step in the journey.
if it the puzzle solving metaphor, i'm taking solved puzzles as pieces to solve a more meta puzzle ... and i enjoying the journey at that level.
i try to practice tracing all the way down the stack and learning about new things added to the stack, but i'm not in it for the sake of the stack or its vagaries and difficulties.
Been looking into community standards issues across different social and ucg platforms, particularly where it seems like cowing to popular politics and not actual questions of law or hate.
Hi everyone. Thank you all for the response to this post. I was at a point of desperation last night and didn’t know where else to turn. The support, concern, and offers of help have been amazing.
I was finally able to have a conversation with my son. He’s still pretty exhausted and jetlagged and I’m sure in shock.
...
I will let you know, he made his way to the customs stand and handed his passport to the agent. He was asked the standard questions and then they put a yellow card in his passport and told him to go to another area.
He said he was in an area with about 10 other people. They would call people into a room one by one. They searched his bags several times. He was then told to go back out and sit down. There was a lot of waiting and watching other people come and go. He said the initial officer searching, appeared to be border control. In addition to searching his bags, they asked him repeatedly if anyone was waiting for him. He told them no his plans were to go to hotel to meet up with family.
After several hours, 2 FBI agents came in. They would ask him questions regarding his feelings towards the president, terrorists, and political memes he liked on Instagram. then send him back out to wait for long periods of time. They also asked him several times if anyone was there waiting for him.
Ess Ess Oh. Understand the number of individual warm bodies who need access to what. In an ideal world (that may not exist) this should be aligned to job description/contract and the process for when those people are removed under any circumstance. Pay for the users you need on the platforms you use, whether that's cloud or resources for on-prem/locally managed tools. Elevate legacy systems that aren't implemented for the scale you're operating at to be managed safely on a per-user level. Tell executives/budget process/whatever/whoever these liabilities exist and need to be covered in budget.
And then, yeah, find a password manager tied into that SSO platform to fill the gaps/enforce policies for users using tools that don't have SSO available.
HR-and-manager-enforceable policies and penalties for users who go off the reservations.
if it the puzzle solving metaphor, i'm taking solved puzzles as pieces to solve a more meta puzzle ... and i enjoying the journey at that level.
i try to practice tracing all the way down the stack and learning about new things added to the stack, but i'm not in it for the sake of the stack or its vagaries and difficulties.