@fullstackchris the "binary search" is just a metaphor for knowing basics of computer science that is behind all frameworks we use now.

Sure, one can miss "binary search" knowledge. But if someone is missing all basic computer science knowledge, than this person is not "senior engineer" but rather "senior [framework] developer"

I got exactly!!! same message no more than 2 weeks ago.

On top what others said, write down his fuckups day by day. When shit will hit the fan, and CTO will blame you for delayed/broken delivery, then you would be thankful for having such diary.

@danielstaleiny one model has boolean property named "IsStoredInDB" indicating if it's already stored in DB (I lost my shit when saw that) 🤣

@l00tbox it's because our world wrongly understands "objective interviews". It's much easier to say that candidate didn't know correct answer rather than spending quality time and assessing ones deep knowledge. The latter is "judgment" which is less objective than A,B,C,D type question.

What is more, the more such people enters this industry, the more they will favour weak candidates, because they won't be able to distinguish good from bad.

Since software engineering gained so much popularity (plus attractive salaries) so many impostors joined that now it is merely possible to win against them.

Maybe in big companies, which can afford hiring best talents.

But all the other small-and-mid companies I guess are sentenced too poor engineers and poor Engineering managers.

@AlgoRythm ouch, such issue, omg 🤣

@ArtOfBBQ i also love freedom, and I agree with you.

My problem is, that so many times "freedom" is used as an excuse to write bad code. Maybe it's just my experience that is negative.

@ArtOfBBQ i know, that it varies. I'm just saying some "basics" that are obviously true, like "have coding standards" or "don't access production db directly" or "don't use patterns if you don't understand them".

I believe that certain BEST PRACTICES are so obvious, that there's no room for discussing the basics.

Or am I wrong?

Bro, exactly. So may brainless folks... You know, IMO to become a proper software engineer one need brain capacity similar to become a jet pilot... Except to become jet pilot you need hell lot of exams etc. while to become a "programmer" all you need is to copy paste some code and fake a CV.

@Godisalie thanks. I appreciate your trial to answer my question. Nevertheless, I was always taught that translating business requirements to IT is a duty of a good senior engineer (or tech lead, whatever), so even in this point I don't see need of technical management, apart from teach lead(s). Thoughts?

What is FP?

@ArtOfBBQ that's why I'm asking. Because from the perspective of good practices, this is how it suppose to be.

So if successful software happens without this practices, then why even bother?

@IntrusionCM have the same. Did you reported state of the project to the management? If 'yes' what was their reaction? Just curious

@AtuM want to share more?

IMHO, we don't such option.

I assume my question is stupid, but anyway: What's wrong with Guid.NewGuid in UTests?

@purist exactly. SO is for asking very specific and concrete questions. If somebody is asking for microservices general question/research or guidance, than it's proper answer to suggest that person doing research first. Because SO is not for that.

Bro, you just described my reality. Are you a clairvoyant or something?

Then answer to the recruiter that "XML is not a programming language" and his Highness Recruiter will reject you from the rest of the process due to not meeting recruitments.

I've been there bro too... Few times. No matter what company's biggest SJW says that everyone can be grown, and that the moron's success is your responsibility - it's not true.

Some people simply can't be helped, and shouldn't be in that industry at all. Money and cosy office work attracted way too many impostors.

Same shit here... I was recruited based on if I know "best practices" (clean code, automated deployment, etc.) In the real job all this doesn't matter. They just want to have legacy shit done one way or another.

Being peaceful? - I agree with it

Accepting broke world? - nope. I want to make a change

Tolerating incompetence? - never!

Lol, you made my day. I have same. I'm saying "let's agree on a generic solution first, and then think about solving exceptional cases", and my manager claims that I am not taking exceptional cases into account.

And there's more like that

@practiseSafeHex yeah, it's so sad you have to get through incompetent recruiter, answer stupid questions, only to be given chance to prove your skills with some competent (hopefully) recruitment manager

@practiseSafeHex you know that recruiter's explanation is B.S? 99% chance that recruiter doesn't have idea what is the job about and/or looking for a unicorn.

@TeachMeCode wrong. A person who lied in his/her CV will get that job. Because anyone who creates such riddicolous JD, will also have broken recruitment process... so yeah

Fuck Apple and their scummy practices.

"kickoff meetings" are an instant boner for managers. They are also proud they did it, because otherwise it would not happen, right?

@iiii true. I should call it "self assigned". Wrong wording in my original rant.

In my place, 50 engineers created messaging based on SNS/SQS. No fucking single of the had any idea about "at least one delivery vs exactly on delivery" and "message duplication".

Than I read docs. Told them. And they were like "oh really?".... and no shit given. No code improvements, no changes.