151 karma · joined June 13, 2011
Besides, test-first development is inherently writing pseudocode where you write MagicFunction() and then TestMagicFunction() and iterate to flesh out both.
Also, who doesn't write a first pass of some code and then drops a comment that says /* handle special cases x, y and z here */ for later?
All of that is pseudocode.
Nodes would include class/object/method nodes w/ code blocks. So, an important AR/VR UX feature would be the ability to collapse/dive-into nodes & groups of nodes much like code-outliners in 2D IDEs.
Another awesome feature would be the ability to affix dials/gauges and other displays to the outside of nodes & node groups that would provide indicators of the unit's state: How "full" is a collection node, how often/frequently was this node invoked, the health of the node (errors, exceptions, slow-execution times), etc.
Let's say there was a 100% effective treatment for cancer/MLS but cost $20,000 per month. We'd all be "willing to pay" for that for a loved one but "willing" isn't "able." That's the problem with US-style for-profit healthcare. Economics breaks down because there's no ceiling to what the "consumer" is willing to pay, only a profit-based decision by companies of how many people it wants to divide into people deserving of health and those not.
Seriously, as a society, if we don't grapple with economic ethics of "miracle cures", corporate greed plus technological advances will lead to endless class wars over who's grandma/child gets to live or who's withers and dies unnecessarily.
I'm no expert but let's say you wanted detailed intel on a oil refinery, manufacturing plant or military facility. With a sensitive enough antenna a balloon fly-by might be able to pick up WiFi signals, keyfob codes, security radio crosstalk, even wireless keyboard emissions.
Also, remember, China has extremely sophisticated facial recognition it uses to track its citizens. A fly-over of a facility at a shift-change could give them a lot of people to target for human-engineering attacks at the site's security.
Levels of control:
# Include my content and tag it with my name for prompts (don't care)
# Include my content but don't tag it with my name for prompts (anonymous)
# Include my content but require attribution if it contributes more than 30% to a piece of output (attribution)
# Exclude my content from your dataset and don't allow my name to be used for prompts (i.e. warn users if they use my name as a prompt)
These "license" levels would allow artists to have some control and could be enforced by bots that send prompts to AI generators & check for attributed or unattributed use that violates the license.
To borrow a concept from cryptography, before now quality art and prose was "proof of work", that is, a signifier that a human or corporation took the time or invested in production of quality. Examples: A well-written, fact-filled article just sounds authoritative & you trust it more. A beautiful, polished book/movie/album cover suggests production-values someone invested because they believed in the product's market value.
Now, if you see quality product art or article copy you'll have to hesitate and maybe do an extra level of vetting to determine if you're looking at something actually good or something whipped up in 10 minutes to just _look_ good, maybe for nefarious reasons.
2) Moderation/Cancelling solved: Allow Twitter users to sign-up/opt-out of content moderation "jury duty." You'd get "Does this Tweet lie or offend standards?" on flagged Tweets. If enough people say "yes", the tweet could be red-flagged, blocked or the Tweeter put on timeout, etc.
3) Faceless Ban Bots solved: Implement a content moderation "Court of Appeals" where a blocked/banned tweet or account could be appealed, again with Twitter users acting as jury. You'd at least get to know why something was banned and get a chance to appeal your case to fellow humans.
Sometimes in an interview when I suspect the interviewer is uncomfortable with assessing "their Dad", I throw a lot of curiosity at them about their skills & career & ask their advice about the company or tech stack they use. That helps breakdown the "too old to learn & won't listen to me" stereotypes.
Once you get the job (although, I highly recommend you avoid taking a job if you get a death march software plantation vibe), you manage high demands by nailing management on requirements and milestones and then out-plan and out-deliver your work so you have an answer for "hey, why are you leaving when we're all working overtime?" If you put in overtime at the start, assist other people and show you can deliver, then they can't give you much grief later.
Also, "cultural fit" questions can be casually ageist as hell. I was asked once (at 40 or so), "We like to skateboard around the office for fun. What do you like to do?" I sincerely believe it was (for the 20-something interviewer) an innocent, almost routine interview question. I diffused the question by saying that sounded like a blast but I prefer Nerf Blaster wars or pranking people by hijacking their wireless mouse or whatever. I got the job offer but I've been on other interviews where I aced the manager's and technical interviews but got shut down by a barely college graduate who clearly didn't think they'd have to work with "their Dad." Not much you can do about that.
For me this means walking through use-cases of an idea "on paper" while resisting the temptation to actually design the solution. Once you've defined the verbs/nouns of the system you're much better prepared to "dive in" and build something. That, in turn, will uncover things your paper system forgot or burst your illusions about certain use-cases causing you to rethink them. Rinse, repeat.
I wonder if that thinking has changed in the age of Computer Science since solving this kind of recursive/iterative problem might open up new ways to analyze algorithms or tackle the Halting Problem for some classes of programs.
Ultimately, the Internet at large needs to grow past this adolescent stage that yields to mob rule and crudely divides people and ideas into "good" and "bad" without any discussion or nuance.
I agree with others that your resume needs to be more accomplishment driven with lots of action verbs and results statements. You want to include a sample (but not a laundry list) of interesting problems you solved and value you delivered. Employers are far more interested in that than who you are and what bag of skills you have. Granted, you need to include buzzwords to be seen by resume filters but your resume should scream "Here's the kind of great stuff I can do for you" in the first few bullet points or so rather than a technical checklist.
I like your idea that freedom and emotion are orthogonal. A lot of the problem we're having with "culture wars" right now is the blurring of the line between the two. I think separating the two ideas might help solve a lot of issues from "cancel culture" to "war on Christmas" and "safe spaces" and maybe even gun control. You can hate/fear/boycott a comedian who offends you but you aren't owed their head on a platter. It's OK to think that your being a Christian/Vegan/Cosplayer is sacred but you shouldn't expect everyone to cater to your belief.
So, there's a sweet spot somewhere between perfect freedom/privacy and perfect accountability/justice. It shouldn't take authoritarianism to sort out but we need to fight hard for the right balance of norms and laws to adapt to changing technology. Should my neighbor be allowed to fly a drone at the level of my daughter's bedroom window? Is it acceptable to record my every move and identify my face in a private shopping mall?