1,308 karma · joined January 10, 2018
I honestly can't decide which would be worse: a developer who literally doesn't know what a cache is or one who installs caches with bad invalidation policies.
That's perfectly encapsulated by a signup/login barrier. Any slick-ness on top of that fundamental requirement is sugar
"There are many different ways to write down the number 5. Tally marks, the sigil 5, 4+1, 2.5 times 2, 10/2. Each of them is more or less useful in different circumstances. The same is true of functions! There are many different ways to write the same function. The mechanics of taking a function in one form and writing it in a new form is called a transformation."
Above needs to be said a hundred times. Then you talk about why a frequency space function can be useful. Then you talk about how to transform a time space function to the frequency space representation.
Most people had a macro invoking "guards" "bank" abd "vendor buy" all at the same time. The interface was mud like and the first (?) command in a statement that was valid would execute.
In regards to staying up to date on php. Surely best practices aren't changing very often? For myself, I look forward to some niceties coming in my tech stack, but I honestly care very little if literally anyone at my org is aware of them. We won't be retrofitting old code and using it in new code will come with all the little gritty interfacing with old code issues that always surface.
So why should I judge them on something that will have little or no impact on their day to day and when it does come around the people who do keep up are more than happy to show it off and evangelize?
In the end all that "work something out" is emulating the counterparty in your own head given their actions and statements.
That emulation will certainly be very difficult when the counterparty is running on different hardware, but it's not impossible imo. And humans get to back propagate error into their emulation model too...
Find the pattern is still the paramount skill, something humans are good at, and will continue to be useful when the counterparty is an AI
That seems an extraordinarily unlikely bar to meet based on my cursory knowledge of where large scale fraud is happening. But perhaps you know more and would like to enlighten me.
Hbase was a pretty solid NoSQL option by 2010, no?
A common refrain from parents in these situations is how strong they thought their relationship with their child was and how they never imagined it could happen to them. Thats scary. Weighing a very low probability extreme consequence vs. various questionably impactful interventions with certain downsides is hard (at least in my view).
Not to mention that there are risks the internet exposes you to that aren't sexual abuse related. Desensitization to violence, insane discourse (epithets dropped like candy), etc are also important aspects of a parent's moderation choices. Trust and conversations cannot address this since the desensitization takes place as a consequence of simple repeated exposure. In the extreme case, desensitization translates to usage, and I think thats clear if you listen to any 14 year old kid on an xbox stream.
1) make that communication remain innocuous long enough to fall into background ignore status
2) escalate in a way that will either avoid communicatong with you or even better seem fine to the child but not to you and so invoke the "my parent isn't fair" response and stop consulting you wholesale
Think of it like security issues where the attackers/researchers are constantly evolving and generating novel ways to hack a system. Your solution is telling fresh out of school developers to be really careful about use after free bugs and spear phishing. Obviously a good start. But it's not enough in a lot of cases.
Imagine pointing a laser at something more than five feet distant the size of an eyeball and then getting another laser to point at the same spot at the same time. And then another five. And those lasers are all attached to cars moving and the eyeball is moving too...
Consider taking a step back. It seems like your worry about becoming complacent is what might prevent you from doing that. If you stay in your current role, try to anyways. Channel your drive into a hobby or personal project or ... Take a month off in order to reset baseline expectations with your org.
Alternating two way stops (n/s at intersection one, e/w at intersection two) seems like maybe an ok way to reduce the problem by half at little to no cost?