Sooooo, those that are cheering on the suffering of someone else are shitty people. Feel how you want, but try to be gracious out loud.

All increases suspended. Some removed retroactively back a couple months. My wife's hours cut, but she works in a hospital and they scaled back temporarily in anticipation of a lot of extra shifts required soon. Can't complain. Extraordinary times.

"Sprints". Scrum and it's philosophies are the root problem. Shit software is achievable anytime with any methodology. Scrum just makes it much more attainable.

@electrineer no doubt there will always be some that discriminate ( in the bad sense of the word). And, the are certainly many places in the world far, far worse than where I live. It's just that I grew up and lived for a long time where "treat everybody the same" was the simple rule to getting along. Now it's all about slicing and dicing us all into the smallest of components and condemning or praising us based on those trivial categories. It's poison, and it's creating a whole generation of bigots who all think they are virtuous and everyone but like them is inherently flawed. I want to never again hear about a movie or book or company board or political body or anything else where the only thing of note is the person's skin color or gender of religion. I want us to act like it doesn't matter again.

All I know is that things were fairly low drama before all this social justice, intersectional, etc. bullshit started. So while I muddled along as a normal mostly nice person, the world changed around me and all I hear these days is that I'm the source of all the world's ills because I can't sneak up on anybody at night and I can pee standing up. And so I'm dismayed at the poison those people spread in the Orwellian name of inclusiveness and fear for my children. Because they are dangerous idiots, and there are a lot of them.

Yes and no. If the media is screaming that the sky is falling and that civilization is about to collapse, I bet the idea would pass through anyone's mind. More pragmatically, if you already have some and you think acquiring more might become difficult, you might stock up for that rainy day. But, while some of that is going on, there is no panic over it like there is over toilet paper.

It works out doesn't work because of the people, not because of the idea.

I'm far more productive working at home. It's not a one size fits all proposition.

@Shiggy "Shouldn't be longer than one day tasks" I've never heard this before. And it's nonsense. Another reason scrum sucks: after complaining that all estimations are flawed and that we should use points or t-shirt sizes, scrum proponents hypocritically assume that tasks estimated using such unicorn fart units are magically accurate and scrum masters become irrationally upset when they are not. News flash, many tasks take longer than a day. Coping them up into smaller bits is just inefficient dogmatism. Plus, doing so leads to piece meal crap software ( pretty much most commercial software these days)

That's the normal state for scrum. Just one reason it perpetually sucks. To fix the suckiness, don't do scrum. Preemptive strike on comments about "devs swarming to help QA, and bs about succeeding or failing as a team": that's called mismanagement and inefficient use of your resources (and another reason why scrum sucks)

I had to look up the word and read about the trend. Then I laughed. It's just old Apple stuff. Any differences are there to make UI/ux designers feel like they've done something new and asked them to market it as " modern" while the thing being done today is now " legacy". It's how they rationalize the need for their jobs. IMO, the designers in our industry are close to useless and initiate more needless rewrites of software than anything else. Just think for a moment of why you would pay again for a piece of software that is functionally identical but looks "dated".

I have explicitly rejected management opportunities at my current job. I think the philosophies and processes are beyond stupid. So, why would I take a position parroting those to those below me. Also, I have fewer meeting responsibilities as a Dev and more flexibility. The downside is the blatant age discrimination. For reference, I have been in a lower management role before at a different company for a short while and while the processes were better, the administrative part of the job is not my cup of tea.

@lamka02sk I disagree as a personal preference. Instead, I use a stack or queue depending on desired processing order. By doing so, any debugging deals with just a single while loop rather than a call stack N levels deep.

Ironically, I doubt I could pass an interview at one of the cool kids companies for a position doing what I do every day because the interview questions do not remotely resemble the actual job.

An 80s hacker? Had the word when come into common usage yet? The only pop culture reference I can think of from the time is the movie "war games".

@lightfulSeer I was not aware there was a swift compiler for Windows. Even then, an online playground can't be sufficient can it?

How's that even possible? Legally?

Something that uses the laptop camera to track your eyeballs focus relative to the landscape outside the car. Take that data and dynamically offset the screen in real time to prevent car sickness when using a computer in the car.

I've never heard of it. Perhaps some more context would ring a bell?

The Atlassian suite is the poster child for why "SaaS" is crap software that managers were suckered into paying for year after year because they can't add. Subscription licences benefit the software seller only. Buyers pay less up front but a huge premium over time. Users get whatever shit gets peddled by vendors that are convinced that more releases equates to quality.

So the purpose was what? To brainwash the participants by propagating stereotypes while ignoring reality. These kind of things seemed absurd in 1984, the year I actually read 1984 in school. Apparently, many people think of that book as an instruction manual.

Ohhh. So that's how stuxnet was deployed.

@VaderNT I disagree (and that's OK). I can be a little more specific by rephrasing my opinion to "code reviews are mostly a waste of time compared to other things you could be doing". Plus, the whole attitude about needing to find something in a code review is a colossal waste. I will never ask for a change related to style or convention or anything else that is not functional (OK, there's bound to be an exception or two but not many). Why? Because it doesn't matter. If I wrap up a complicated set of changes and spend 3 days shepherding it through a maze of Jira hoops and countless build failures due to unrelated tests only to have a reviewer tell me I should expression based properties because they are "newer". At that point, you're just taking the company's money and setting it on fire. If it runs and is reasonable, move on.

If I am unfamiliar with the area of code then I scan it quickly for obvious pitfalls. Sometimes that means the review lasts less than a minute. If I am familiar with the area or have concerns about what's being done, I will fetch the branch and run the code as well as look at the code. Max time for that would be about an hour. Spending more time if governed by the law of diminishing returns. My opinion: software reviews are mostly a waste of time. Sure, they do catch some things, but don't spend a lot of time on them.

Former disgruntled employee.

It's not that I hate any language. I have reached the point where I hate learning new ones, though ( because it means I'm having to learn the same old things all over again because language "blah" is the new hotness when I can already do all that hotness in 4 other languages)

My wife and kids think it's awesome.

Yeah, there's no way from just looking at the code to know what type or types of things are stored as the dictionary values.

I've used it for 95 percent of my (admittedly fairly simple) image needs for many years. Even simple stuff like measuring distances in screen captures. It's absolute nails at doing what it's intended for. And free. By all means use something else if it does not fit your needs, but I don't see how it deserves any serious criticism.

Actually that's a great representation of agile software development. If a quick execution of the software does not yield satisfactory results, iterate ( perhaps using a double or triple fold depending on the size of the problem/solution gap). Regardless, every iteration of the software is flimsy, disposable, and ultimately smells like shit.