Seems to be the MO around here - create and profit off of horrors beyond our wildest imaginations with no accountability and conveniently disappear before shit hits the fan. Not before writing an op-ed though.
It never occurred to me that a rebuttal to "not using lines of code or bugs solved because it can be gamed" is just to point out productivity is literally always gamed
Edit: Anyways I like this. Love the idea of companies taking over for helping out the underrepresented in their ranks. This is a natural progression from remote work.
Sometimes I look at stuff like this and sit in despair that I'm not learning anything that will let me work these kinds of problems while I work at a defense contractor maintaining 20+ year old code.
The only person doing this mental chase here is you. Why don't you just come out and say what you mean?
If you're really this confrontational about "the color" black being tied to darkness since pre-history (not much of a stretch there) and the significance of darkness being the physical manifestation of something like "evil" (also since pre-history) EDIT: and why "evil" is "intimidating", then nobody should take your contributions to this discussion seriously.
EDIT: I just don't understand how your response of "if black is intimidating, why do they paint them tan for military use" is in any way an honest argument. Did you simply not even think of camouflage? There are more important tactical advantages in warfare than intimidation. And now I feel like I did the job that darkserside was trying to avoid.
Don't the heads of state for the EU decide who the EU council president is? Should each head of state's vote be given equal weight considering the vast differences in population of each EU country?
Back in my teens (mid 20s now), I was very (very) interested in Photoshop to the point where I would consume dozens of tutorials a day and just work on projects for things like forum signatures or post headers and graphics. My "graphic design" career never took off, but to this day I still have muscle memory of certain tasks and actions I've created and still set up my workspace in the same way.
Now that I'm a programmer I rarely find the itch to dive into things like this again. Every now and then, I'll want to create some silly website with a game or something and again I'd find myself spending late nights just working on it. I've realized that the fact that I "know something" isn't what drives me, it's that I'm interested in what I want so much that I'll learn anything just to get to do it.
Lately, I've been starting to feel the itch for doing something related to baseball (again, something I love), like data analytics or amateur scouting or something. I have no idea how to get started, but I just know I want to. I hope I find tutorials from people who are just as excited to share information as I am to absorb it.
I think a) we may have different definitions of "military aggression" and b) China and the US have different "priorities" when it comes to the military.
So here's something I've been thinking about recently. I'm 2.5 years into my first job out of college and I think I'm starting to pick up on things like "oh let me guard against something that could return null" or "let me guard against calling .at() out of bounds". I'm starting to feel really thankful that my work has me thinking like this, because I can actually see it as a sign of getting better as a developer.
So -- instead of wondering what kinds of problems will get me through interviews, do you think some way I can train myself to be able to see things like that more often? "Defensive programming" or something?