Nice.Except for the handsome, imposing, CEO, horny, and flirty parts, you’ve got me pegged!
(I’m a troglodyte who just drags them into my basement.)
What Are You Doing Right Now? (1,012 Viewers)
- Thread starter ßöмßäяðîëя
- Start date
- Tags gay space iliveforfinasteride iliveforjuve is not white lionsheadsmellsliketrash loldevil size queens sweet matt is sweet errwhere virgin devil
Nice.Except for the handsome, imposing, CEO, horny, and flirty parts, you’ve got me pegged!
(I’m a troglodyte who just drags them into my basement.)
Mine is new to our team (probably number 10+ since I've been on the team) and based in India, he was ready to go to war today to convert a bug to an enabler. There was no benefit or purpose to this, he just REALLY wanted to do it for reasons that I cannot fully understand.
Today I was working with multiple devs to try to fix an issue I was testing, didn't get it done by end of day. Maybe even can't because of permission issues. I can't wait to hear the asinine bullshit he's going to come up with tomorrow as an offering to the religion of nonsensical processes.
"Can we move this to 'In Progress'/'Code Review'/whatever?" BITCH no, it would be there if it was supposed to be there. Goddamn, shit drives me up the fucking wall.
Today I was working with multiple devs to try to fix an issue I was testing, didn't get it done by end of day. Maybe even can't because of permission issues. I can't wait to hear the asinine bullshit he's going to come up with tomorrow as an offering to the religion of nonsensical processes.
"Can we move this to 'In Progress'/'Code Review'/whatever?" BITCH no, it would be there if it was supposed to be there. Goddamn, shit drives me up the fucking wall.
Sprints are problematic for the simple fact that they never let up. Sprints are not simply shorter deadlines, encountered sporadically as you move along. They are forever repeating, back-to-back deadlines. Waterfall was structured around genuine deadlines and real-world events that demanded focused attention. You worked hard to get something working, then you were done. High pressure was followed by low pressure. Sprints, on the other hand, are fake deadlines, invented for the sake of a process. Since they are contrived, they have no natural breaks or resting periods. There is no time to breathe. There is no autonomy.
When a sprint begins, the expectation is that the time for preparation has passed, and only implementation remains. Scrum seems to assume you can simply "bang it out" like assembling a fucking piece of IKEA furniture. Just pull the next instruction manual from the backlog and follow the steps. In reality, it's more like being dropped into the jungle without a map or provisions, with only two weeks to find your way out.
When a sprint begins, the expectation is that the time for preparation has passed, and only implementation remains. Scrum seems to assume you can simply "bang it out" like assembling a fucking piece of IKEA furniture. Just pull the next instruction manual from the backlog and follow the steps. In reality, it's more like being dropped into the jungle without a map or provisions, with only two weeks to find your way out.
Had an interview today for a publicly traded firm in the tech/health space that went so well that the VP told me he was passing me along to the final round at the end of the interview. I don't think I did that well, but whatever, I'll take it. I think I can only convey 50% of myself because I fucking hate interviews. But this was shocking to hear because usually I get a rejection email afterwards.
I think the more infuriating thing than the sprints themselves is all the nonsense ceremonies created around them. Sprint retros, sprint demos, sprint metrics meetings. Every fucking three weeks. Nothing ever truly changes in most environments within the cycle itself, because good teams already share feedback and act collaboratively, regardless of schedules. Having a shared service imposter forcing you to do something for the sake of a fake process is anything but instilling trust and collaboration. Most of the time, the problems that need to be solved are beyond the competency of the scrum master and he/she can do nothing to resolve them, nor can their leadership in an aPMO because they don't understand the product or business either. So in fact, it actually does more to harm progress because it doesn't occur organically and there is no incentive for overperformers to care about a retro because it should be done on the fly anyway. If not, it needs a dedicated meeting with a focused group.
I think the more infuriating thing than the sprints themselves is all the nonsense ceremonies created around them. Sprint retros, sprint demos, sprint metrics meetings. Every fucking three weeks. Nothing ever truly changes in most environments within the cycle itself, because good teams already share feedback and act collaboratively, regardless of schedules. Having a shared service imposter forcing you to do something for the sake of a fake process is anything but instilling trust and collaboration. Most of the time, the problems that need to be solved are beyond the competency of the scrum master and he/she can do nothing to resolve them, nor can their leadership in an aPMO because they don't understand the product or business either. So in fact, it actually does more to harm progress because it doesn't occur organically and there is no incentive for overperformers to care about a retro because it should be done on the fly anyway. If not, it needs a dedicated meeting with a focused group.
Data protection is pretty much its own field of law and is often relevant in litigation as well.
Personally I often deal with cases that involve the Belgian and European equivalents of HIPAA as one of my areas of expertise is insurance law and which access insurers can have to medical files and under which conditions.
Personally I often deal with cases that involve the Belgian and European equivalents of HIPAA as one of my areas of expertise is insurance law and which access insurers can have to medical files and under which conditions.
During my master’s, courses like Management Information Systems, Enterprise Architecture, and Impact of Technology on Organisation and Management introduced me to the foundations and requirements of frameworks such as GDPR, NIS2, and HIPAA. In Data Mining and Data Warehousing, I also worked on technical aspects of data protection like anonymisation and privacy. And through extra reading and course projects, I became familiar with emerging regulations like DORA and the Cyber Resilience Act.
What’s interesting is that most companies list this kind of knowledge as a requirement when hiring security specialists. I initially thought this area belonged only to IT, but I later realised that in law, these topics are also fundamental except that law focuses on process, frameworks, and compliance, while IT also covers the technical and implementation side. That overlap has opened up a wide range of career opportunities in security and compliance.
What’s interesting is that most companies list this kind of knowledge as a requirement when hiring security specialists. I initially thought this area belonged only to IT, but I later realised that in law, these topics are also fundamental except that law focuses on process, frameworks, and compliance, while IT also covers the technical and implementation side. That overlap has opened up a wide range of career opportunities in security and compliance.