There are no TLS certs, it's x509 certs :) SSL certificate is still the name used by everybody though. For the protocol, TLS is correct (apart from SSLv3 which is very deprecated).
My sincere condolences to the author. Wishing you strength and peace.
I once saw a man have a heart attack on the beach, less than a 5 minutes drive from a fire-station and rescue team. A helicopter arrived after 45 minutes, and the man was deceased already. That was in Martinique, french Caribbean.
There's a need for an app to let patients track the ambulance. It's been possible for 10+ years, as seen with Uber. It seems existing products have focused on tracking only for the purpose of managing a fleet, missing the focus on patients needs.
Personally I see plenty of problems with a real-time public broadcast of all the addresses a medical event has occurred at, the patients' location in transit, and the hospitals that received those patients.
"Ambulance chaser" is a rather derogatory phrase for a reason.
there's no need to post 7 digits accurate GPS coordinates, the important thing is to have an understanding of how many are how far from where they are going to, ETA, what's the capacity (free units ready or cars yes crew not, or vice versa)
An emergency dispatcher could send a Text message back with a link to a private, case-limited, web page with an ETA + a map + the ambulance location in real time.
See? no "real-time public broadcast of all the addresses a medical event has occurred at".
This would be a great way for thieves to determine which house is likely to have just had everyone leave it in a hurry and not likely to return any time soon.
$1465: That's what a nylon+paper bag from Issey Miyake costs. Then the price of this cut-up sock makes sense: it's not an iPhone accessory, it's a luxury fashion item.
Suffered a stroke in 2004 (migrainous infarction). Became half blind. Rested for a good year.
Became a photographer for 8 years, then switched back again to software development.
From then on, the limits were: WFH only, limit stress, run away from job if things go bad again. Nap if brain feels exhausted. Sleep, more and better.
20 years later (53yo), I'd say I'm doing great! Also fitness helps remind me to take care of the body...
Tech has built literal industries of people trying to stress you out, and they mostly don't have actual tech skills or the empathy that comes with them so back it up.
For me, I usually try to avoid anything where the working practices are strongly defined. Agile has long been a bad word.
Unfortunately while the intentions around agile were noble it's pretty much a direct way to burnout or worse. The human mind is not designed to "sprint" run a marathon, metaphorically speaking, forever.
I see older devs being active in the trade well into their 60s but even as I much younger person I don't see how agile development is sustainable for a ~50-year career.
The thing is, the core agile points from the manifesto are pretty much universally fine and can pretty much be boiled down to, "make changes fast, get feedback, gain more understanding faster".
Pretty much everything that's been layered on top though has either nothing to do with the manifesto, or actively breaks it. i.e. there's a burning issue, I'll get to that after my sprint commitment, which was sold to let me finish work, but now only exists to stress me out to squeeze more widgets per unit of time, where the widgets pretty much never actually map back to anything actually tangible.
Scrum is like Spaghetti Carbonara in America. The ingredients are simple and there's a tiny bit of technique involved that anybody can figure out after a few tries. For some reason though almost everybody that makes it decides that they know better than the people that invented it and so adulterates it with peas and onions and garlic and cream and cream cheese and Italian seasoning and parsley and chives until it ends up being Olive Garden Alfredo. If they wanted Carbonara then they would have cooked the Carbonara, not the waterfall with a bunch of JIRA workflows and four-hour meetings layered on top. They just did what they would have done anyway while attempting to sound fancy via obfuscation.
It's not just Agile but the same applies to DevOps.
DevOps is a culture. It can also be the specific subset of highly skilled individuals who were part of or an outcome of said cultures cross pollination. Today DevOps most often means fairly unskilled person hitting pipelines with hammer.
In the end, the same old people with the same old commercial interests adopted the term in a way that benefited them but changed the meaning of the term because change was not actually something anyone wanted.
That's not actually true. To give a silly example: does anyone (seriously) claim that 'true fascism' has never been tried?
Or: liberal democracy (I'm sure you can find a synonym that ends in *-ism) has been tried. It's been doing ok-ish. Obviously it has warts and all. But more importantly: approximately no one ever seriously claims that 'real liberal democracy' hasn't been tried.
Similar for constitutional monarchy, or 'social market economy', or dictatorships, etc. People can mostly agree that the real deal has been tried.
Any principle or practice falls apart when tied to an economy. See also: religion, politics, society at large. I don't foresee that changing in our lifetimes, so make money doing it the wrong way, and do it the right way in your free time.
I don’t agree with that though, plenty of places practice agile well. Maybe big corporations don’t practice it well, but startups often do agile correctly and understand the philosophy.
Inasmuch as Agile was adopted at companies, it's because it was sold to them as a way to provide greater transparency, accountability, and control into a chaotic software development process. The vice president behind the company's "Agile Transformation" probably can't even name point one of the manifesto; "we're doing Scrum with JIRA, therefore we're agile" is the extent of his concern.
You say that, but it was way more stressful pre agile with the fixed date, fuck around for a few months planning, then dev, run out of time then death march to finish, etc.
A lot of young guys like that D-Day style work, then goof off for a while, but not me. Continuous sustainable work is much preferred.
There's a difference between "bad PMs using the tool wrong" and "ordinary, human PMs using the tool in the way that common business incentives would lead you to predict they'll use it".
If the tool is used wrong most of the time, it's at least partially to blame.
"If the tool is used wrong most of the time, it's at least partially to blame."
Only if there were other tools that didn't fall victim to the same business incentives, but they all do.
I've had PMs that find a balance with the business incentives and make it work. If you’re human and make the wrong choices, then most people, including me, will likely call you bad in that context. If they can't stand up to find balance with the business incentives, then they're a bad PM. That doesn't make them a bad person.
I have seen Scaled Agile Framework (SAFe) work in multiple real program teams. Doing it successfully requires total commitment at multiple levels and many organizations are culturally incapable of making the transitions.
To be clear I am not claiming that SAFe is necessarily the best possible methodology. There is certainly room for improvement. But empirically it can work in real life.
The organizations I've seen do SAFe at the top level "coincidentally" have so much in the way of resources that if they do software at the group level at all, they do it like a gentleman farms.
"I mean if something doesn't ever work in real life then its not good."
Are you talking about Agile, Waterfall, or project management in general?
I've seen Agile work just fine. I've also seen it fail miserably. I've seen both of these at the same company with the main difference being how aggressive/delusional the leadership is. The easy test is if your leadership is legitimately ok with your team going home early if you complete your sprint commitment early, and it actually happens on occasion.
It feels like over the past decade or two, every company that builds software has gradually adopted the same terrible practices as is commonly found in game development studios.
That is why more advanced agile methodologies such as SAFe use the neutral term "iteration" rather than "sprint". It doesn't imply anything about team velocity or individual workload.
The term "iteration" was in common use by many of the big 90s proto-agile methodologies (think RUP et al). And XP - which I guess is what most people would regard as the first "true" form of agile - used it too.
SAFe is just an attempt to mush something that like looks like agile to delivery teams together with something that fits into more traditional program management, governance, and strategic direction lifecycle models.
There's no particular magic to it, and it's probably better to think of it in terms of being an "enterprise variant of agile" rather than a "humane variant of agile".
Yes, that's accurate. In the real world sometimes software programs have to make compromises in order to align with actual business needs. Like if you're going to be manufacturing hardware to go with the software or scheduling training for users then you have to apply strict program management discipline to ensure everything comes together at the correct time.
Sure, that's fair. In the real world there are a lot of developers who want to be told what to do, or need to be told what to do because they lack business domain knowledge. A defined methodology like SAFe allows large enterprises to move forward at a steady pace and get some productive work out of those people.
The reality is that in some domains there just aren't many developers who are highly motivated, self directed, and thoroughly understand customer needs. Those people just aren't widely available in the labor market regardless of wages or working conditions. So if management doesn't impose a fairly strict methodology then then the program will collapse.
I'd make a separate case that learned helplessness is a reversible thing, and more highly motivated and self directed devs can be grown.
But leadership has to incentivize not just being a ticket monkey, and needs to mindfully empower people. You can't just flip a switch in a feature factory and say "fly my pretties, be free!"
Sure, that's also fair. But it takes a long time to turn culture around. And in the meantime the company has to continue shipping releases to customers or else they run out of cash and everyone gets laid off.
In my experience of it though (only two workplaces, but not one) it's used for higher level planning, rather than being a 'more advanced agile'. I.e. a SAFe iteration spans some number of sprints greater than one. What are we going to deliver this quarter versus how are we going to break down and monitor progress of the quarter's deliverables week by week. (Don't read that like I like it.)
I think you're confused about the terminology. SAFe doesn't have sprints. Depending on the program planning horizon, several iterations can be grouped together into a larger program increment which typically lasts about a quarter.
Why is anything supposed to be sustainable for a ~50-year career? That’s a long time! Things change and people change.
It’s not like my great grandparents had a passion for farming in South Dakota and that’s why they did it until they dropped dead. It’s all they knew and what they did to survive.
If you gave them the option to tap on a keyboard in an air-conditioned room for 10 or 20 of those years they would’ve taken it.
Agile (or rather modern management) converts human capital into capital as fast as possible. Considering the endless supply of developers and lack of accountability there is no downsides to doing that, you are an externality.
Reminds me of this Indian boss I had whose only agenda used to be calling me up and telling me that others had complaints about my work. After 2 years of listening to his stories, I had to tell him off one morning. I quit about 4 months later. The guy was a completely talentless aggregator. I don't get how some Indian firms promote people and this wasn't a small firm either. He ended up being promoted upwards.
> For me, I usually try to avoid anything where the working practices are strongly defined.
I'm grateful I've managed to avoid this so far. My favorite place to work has been more akin to "we need X done in Y system before Z date, but how and when it's done is up to you".
The worst part is how these people almost always work on the most boring, rote crap. They could be selling mens hair loss medication on the internet (cough) and key individuals in the organization are convinced what they do is life-and-death, future of humanity, work nights and weekends, we're the next Google. It's so deeply cringe-worthy. Meanwhile, I know a ton of people in the traditional pharma industry (e.g. not Novo, but Novo-adjacent); those companies broadly treat their employees pretty well, very minor amounts of overwork, they're well-staffed, some still have pensions, people spend their whole working lives there.
Tech sucks. It's filled with talentless hacks who think "because we use computers" means you've got a blank check to make every individual do the work of three individuals. And then your company gets gutted by private equity anyway, because it turns out hiring talentless hacks and overworking has consequences.
This is a weird take, but I genuinely and deeply believe the world would be a far better place if everyone experienced a life-threatening but recoverable major medical event and/or had children, while young. Perspective-shifting events that are core to the human condition and help ground your reality in work not being everything. By the way: The businesses our society would build would also be stronger.
> WFH only, limit stress, run away from job if things go bad again
I’m facing a similar set of health-based restrictions, it’s edifying and impressive how you’ve pushed through. I’m curious: how do you broach this with potential employers and shape your job search/career path around it?
Applying for pure remote positions puts one in direct competition with younger people who can pull obscene hours with no accommodation needs. Leading with disability/accommodation needs feels like the opposite of the ‘best foot forward’ honeymoon phase salesmanship associated with new jobs, and kinda soul crushing regurgitating the circumstances for chronic illness while hoping for a job. And uncontrollable management changes can eliminate medical protections and acceptable working environments, leading to an enhanced need to be able to hop jobs (exacerbating both the previous situations).
I’m fortunate my primary skills are amenable to straightforward accommodations, but you gotta get the job to do the job…
> kinda soul crushing regurgitating the circumstances for chronic illness while hoping for a job
I have to do this every time now because I have a resume gap. I don’t have to explain in detail, but even revisiting those three years for a brief explanation sucks.
I’m sure there’s an implicit realization that I will likely ask for accommodations when I explain the gap which likely reduces my chances of being hired.
I'd be interested in how you managed the impact to your vision, any particular technology improvements you made? My dad had a stroked over the summer and lost vision on his right side - he's older but still works at a computer and is pretty particular about workflows so I don't want to muddle with what works for him too much.
Hi! I hope your dad gets better soon. My vision got better over 3 months, then more slowly over a year. I keep a "small" blind spot in my field of view (where I can hide my hand).
I didn't need more management of this condition but rest.
I remember the first months, trees felt exhausting to look at because of their complexity, and I couldn't watch an action movie because it felt too intense.
Given enough kids to take care of, a mortgage and other financial/dept obligations, your insurance money might be just a drop in a bucket and your only destination will be a social welfare system. And even that might not save you from having to sell your house or apartment.
This feels like a very naïve viewpoint.
The reality being that you can't rely on insurance at all. You might have insurance but that certainly doesn't guarantee you'll be financially supported through health issues. You'll also be required to engage in legal battles with your insurance company which might be prohibitively complicated after a brain injury.
I got unemployment assistance, I'm french and lived in France at that time.
Be it family, savings or social security, I didn't take a year of vacation. I was trying to pivot to another activity which is difficult in itself, more so after a stroke.
Also before you tell me how good social security is in France :-) you must know my doctor likely caused or amplified the stroke by giving me the wrong treatment at the wrong time, and by not telling me to go to the hospital before 3 full days... and then they let me out. I returned urgently the week after, when a neuro-surgeon freaked out.
No, at least in Germany (pretty sure other western countries too) you are covered after stuff like this. You won't be rich, but enough housing food and your camera.
I'll modestly add that my sight was getting better and wasn't really an obstacle. It started with an activity of carbon ink large format B&W art prints for other photographers... then I became one too.
The "irony" didn't appear to me at that time, someone had to tell me it was ironic!
Why do you guys downvote - is it because the comment sounded snarky? It wasn't meant to be, I think it is (obviously) an impressive feat to work as a photographer when your eye sight is severly limited.
As a migraine sufferer this sounds scary and only today I have learned about it. What was it like? If I may ask. Is there a way to prevent it? I googled it and it seems to appear rather arbitrarily and suddenly.
It's very rare. I was a migraine sufferer, but this is how that time it was different:
- I was under severe stress at work
- I woke up with aura, realised it when looking at the mirror, I had only one eye
- visual symptoms (aura) didn't go away after 1 hour. That's the limit where you MUST seek medical advice
- having "a migraine" that day raised my stress level... because work...
- symptoms persisted... and after getting better over a year, what was left became permanent (blind spot where the migraine started in my field of vision)
DO NOT take triptans during the aura. DO NOT take any vasoconstrictors during aura, since it's a phase where blood flow is restricted. That could have caused my stroke.
When a migraine hits, I take aspirin, stop all stressors, ALL stressors, try to calm down (I've used anxiolytics occasionally), breathe and rest. I'm often off for 2 days. It happens about once a year.
Again, migrainous infarcts are VERY rare. You'll be fine, just let the aura pass, and know to seek medical attention if it doesn't.
You know what was an actual issue, that any AI would have correctly identified as an issue, but HackerOne dismissed? the 1.1.1.1 rogue certificate that later made the news...
I built https://SSLboard.com to manage your certificates at any scale and see what’s deployed, where and how. It’s using Certificate Transparency to inventory your certificates so it requires minimal input but provides a complete audit of deployed certificates.
Automation isn't enough: qualys.com (famous for SSLLabs.com) is currently serving an expired certificate (expired 8 days ago). They know their job very well, but without a tool to thoroughly and systematically inventory your certificates, you'll miss it.
"Although your finding might appear to be a security vulnerability, after reviewing your submission it appears this behavior does not pose a concrete and exploitable risk to the platform in and on itself. If you're able to demonstrate any impact please let us know, and provide an accompanying working exploit."
I was disappointed, and as far as I'm concerned, HackerOne is 2/2 dismissals.
