- Link: The Faces of Evil
- Zelda: The Wand of Gamelon
- Link's Crossbow Training
- the various Hyrule Warriors games
Good luck! :)
724 karma · joined August 23, 2010
- Link: The Faces of Evil
- Zelda: The Wand of Gamelon
- Link's Crossbow Training
- the various Hyrule Warriors games
Good luck! :)
People remember the emotions the artwork engendered, and thus the whole work is associated with the feelings, flaws and all. If the work is particularly widely known, the flaws can become a stand-in for the work itself.
I see this in video games - I'm fond of the NES-era "flaws" and limitations (palette limits, sprite limits, sound channel limits), but less connected to the Atari 2600 or SNES/PS1/NDS/etc flaws. Shovel Knight is charming; A Short Hike, while great, doesn't resonate on a style level.
It sorta worked, and sorta didn’t. I’m seeing no evidence that this round is different. LLMs allow coding via natural language and assuming a lot of context that is typical to human conversation, but a lot of coding is delving into nuance, which is going to be work, no matter the tool.
Currently, this is “Working as Intended” in Canada’s political system.
A lot of the “big lists of controls” security approaches correspond to duty ethics: following and upholding rules is the path to ethical behaviour. IT applies this control, manages exceptions, tracks compliance, and enforces adherence. Why? It’s the rule.
Contrast with consequentialism (the outcome is key) or virtue ethics (exercising and aligning with virtuous characteristics), where rule following isn’t the main focus. I’ve been part of (heck, I’ve started) lots of debates about the value of some arbitrary control that seemed out of touch with reality, but framed my perspective on virtues (efficiency, convenience) or outcomes (faster launch, lower overhead). That disconnect in ethical perspectives made most of those discussions a waste of time.
A lot of security debates are specific instances of general ethical situations; threat models instead of trolley problems.
Same with “hire smart people and let them work”. When salaries are relatively low, consequences are limited and incentives are well aligned, that approach works. As soon as any of those things change, then the “manager mode” fails dramatically.
As someone who ascribes to “manager mode” most of the time, I’m going to start looking more at places where the assumptions break and (carefully) try out “founder mode”.
Hardware, software and firmware are all prone to mistakes, errors and corner cases that are surprising. Security issues generally live in the intersection of systems with different metaphors. Hardware is not immune from issues, and software can help reduce that impedance mismatch.
[0] Found an instance here, no claim to its veracity or safety: https://www.gherush92.com/documents/744E.asp?type=2&file=C%3...
The GP point is correct; we implicitly convert between all these representations naturally and quickly, but there are interesting branches of mathematics that consider those conversions explicitly and find nuances (eg, category theory).
After (fairly) long time in the industry, it seems to come down to:
- understanding what one's clients need (not what they ask for)
- understanding what's in the realm of the possible (technically, politically, organizationally)
- understanding what are the possible futures (good, great, and abject disaster)
If, after answering all those questions, one still advocating for a rewrite, you've shown the maturity needed to undertake the effort.
"Finger-gunning" is usually related to skipping those steps, not the ultimate decision.
(edit for formatting)
The “real world engineer” job exists, it’s a security engineer. And it’s equal parts awesome and draining.
It sounds like blocking calls switch to a system stack and return the Go stack to the executor pool, but I don’t have source links to back up that claim.
(I am also deeply skeptical of these frameworks, but don’t have a strong argument against them, and they seem pervasive in the security industry)
I think that speaks highly of the Ferengi social system.
I have an OP-1 and a collection of pocket operators. The PO’s are my favourite creative outlets, by far.
The Halting Problem is a truly interesting result, and for the most part uninteresting in practice.
There is a solution to the halting problem. It’s that it is undecidable.
The key point in my view is “control”. You’ve referred to Uber.com/Xmas-sale as an example where Uber the economic entity is in charge of their own shortening and therefore avoids the problem. However, Uber the company may fall on hard times, sell their real and intellectual property and we’re facing the same issue of a lifetime mismatch between an owner and an URI.
Incentivized blockchains are theoretically singletons and perpetual; the worst case of a history rewrite is economically disincentivized. The lifetime of the URI database exceeds the URI lifetime.
In practice, I agree with you that companies should ensure control over their URIs over their lifetime. The advantages of a blockchain approach are far outweighed by the current downsides.
Exercise left for an interested reader, which sounds like isn’t you :)
Full disclosure: I work at Google, but nowhere near the chatbot stuff. This is my humble opinion and nothing more.
2% inflation is not a natural state of affairs, it’s a target that’s considered the “appropriate” amount of inflation.
Computer security is a lucrative field, and a broad one.
You could continue the bug bounty approach, which leads into vuln selling (with the attendant morality questions). You could go into systems security research, a long term project but worthwhile intellectually. You could contract (needs networking and business), you could FAANG (needs patience and soft skills), you could government (needs patience and more patience).
My advice: don’t rush. You have at least 50 years of career ahead of you. The decisions you make now will influence your direction for years, but there’s very little you can do to completely derail your future. Try some things, see what resonates and clashes and learn more about you.
Context: 25 years in computer security in a variety of roles, currently FAANG, currently management. My 17 year old self would likely be somewhat surprised at my circumstances, but hopefully not upset :)
It’s mostly tactics on how to negotiate well, and one piece of advice I’ve adopted is to start my questions with “what” or “how”, not “why”.
“Why” comes across as interrogative; forcing “what” or “how” creates enough time to reassess the actual uncertainty and rephrase as a curiosity question, not an implicit accusation of wrongheadedness.
“Why did you choose this algorithm” becomes “how did you choose this algorithm?” or “what factors did you consider when choosing this algorithm?”
It can be manipulative when done in isolation. My other main takeaway from the book was to have a genuine interest and concern for the other person’s needs, even when you disagree.
Between the trick and the mindset, I’ve found it’s served me well.