When I worked for an online dating app, at one point we had the ridiculous idea to try to take a popular LinkedIn feature and convert it to a dating app feature in order to capitalize off of the success LinkedIn had with it.

The feature was LinkedIn endorsements. The idea was to allow the dating app users to get endorsements from people in their contacts lists on certain traits/features from a defined list (ex. Funny, smart, etc.). It wasn’t a terrible idea on the surface, but the way we planned to execute on it was insane and everyone knew it was going to fail. To avoid any controversy all of the endorsable terms were watered down to the point where no one would ever find using them/asking their friends for endorsements to be any fun. And the worst part was how we planned to get people to ask their friends for endorsements - management wanted us to build a contact list importer and just spam email contacts with “please endorse me” emails. The whole thing was ridiculous.

No one, including myself, wanted to build the feature/spam tool but management really wanted it so we had to build it. Like expected, it failed very quickly when it was clear no one cared about getting their real life friends to endorse them on some dating app, and the spam contacts took was ineffective and... spammy.

Apple has programmed an avatar maker in iMessage that generates emoji that are supposed to resemble the person. However it does not have any setting for facial structure to represent a person’s sex. I’m pretty sure they did it because “gender is a construct”.

When I was growing up I had some issues with gender dysphoria. I am male genetically. I was mistaken as female my whole childhood because I was “pretty”, my best friends were girls, and I liked cooking, drawing, and dancing. Puberty happened and I started to look like a man. I considered transitioning because I felt female but I decided to let my body do what it wants and do the things I like to do without worrying about if they are gendered or not. I am married and male and I like what I like.

This stupid iMessage avatar. I have tried my hardest to make it look like me. I have long hair and keep my facial hair clean. They don’t have a switch to change some facial physiological traits so I have this Memoji that looks like a woman with a slight hormonal imbalance. It makes me feel conflicted like I felt when I was young. I haven’t thought about it in years and now I feel like I have an uncomfortable secret female avatar that i carry around on my phone and I feel like I’m carrying a secret.

A persons genetics result in differences in facial structures. Biological sex is more than the length of hair and whether a person wears makeup. I hate this “sex is a construct” trend. I’m fine living my life, but then companies push this software onto my phone like propaganda. I want it to look as masculine as I look IRL.

I learned a valuable lesson today about the life of a manager. I’m not a manager, but I am a senior level dev.

Today I was told there wasn’t room on the new team for 1 person, and I had pick that last team member. I had to choose between a friend who really isn’t cut out to be a dev and a non friend who is a better dev.

I talked through my reasoning and ultimately chose to put the friends job in jeopardy. They told me that I had solid leadership traits for being able to separate my emotions from my decision making. But I felt like a piece of shit.

I cried back at my desk. The friend doesn’t know yet and I can’t tell them. Is this what execs feel when they have to let people go?

Dad?.. what is a super hero?
- it's an hero amongst heroes. oftentimes ordinary heroes inherit traits from super.
It's basic inheritance, son.

Do you think being a great software engineer is simply hard work and passion?
Or there is also a component of natural affinity, certain personality traits, etc.

!dev-ish

I hate whenever people take hobbies and other things that aren't personality traits and try to make it a personality trait.

Your sexuality isn't a personality trait.
Your diet (looking at you *obnoxious* vegans) isn't a personality trait.
Coding isn't a personality trait.
Your race isn't a personality trait.

I'mma end this rant with a !rant tho.

I know they're obnoxious asf but oh my God mechanical keyboards are one of the most amazing sounds on this earth. Sometimes I'll type just to hear that beautiful sound.

!rant
So, Rust again.
When I learned that Rust doesn’t support inheritance, only traits (interfaces), I was shocked at first.

Then I tried to remember when the last time was that I have used inheritance in the code that I write (not the code that I use).

And I could remember an instance some months ago. But I also remember that I was very unsatisfied with that design and refactored it to use composition instead. And it was much better.

One of Rust’s properties is that many good practices in other programming languages are enforced rules in Rust.
And in case of inheritance, it seems like Rust decided that composition over inheritance is such a good practice that it should be a rule.

I’m not 100% convinced that there never will be cases where inheritance is better. But I still like this radical idea of forcing the devs to do it "the right way" in the majority of (if not all) cases.

I think many devs will disagree.
What do you think?

The people. I find devs to be (obvious generalization) prone to: not take criticism, not understand the difference between fact and opinion, not understanding that it is perfectly acceptable to change your point of view when presented with new information that will conflict with what you currently believe in. It is a sausage fest brought to you by eons of very fragile male ego in the making, and many other qualities that were very much diluted in a lot of the other fields I have worked on: from retail (shitfest) to import/export all the way to military (another shitfest, for different and rather dangerous reasons).

I have met some amazing people in the field, don't get me wrong, but the quirkiest of mfkers i have met make me believe that maybe I AM the one that does not belong in the field (top kek).

On a more technical side, basic stuff like reading comprehension, attention to detail, the ability to translate complex problemd to pieces and that interconnect among the themselves, the ability to understand the grand mathematical scheme of things, the ability to be patient and despite what the above generalization would have you believe...the ability to communicate with other humans with tact and understanding as well as a spirit of collaboration, etc etc, are definitive traits to consider if you want a career in software development that leads above just being a code monkey.

Shit like that.

Should I be excited or concerned?

Newbie dev(babydev) who just learned string vs int and the word "boolean", is SUPER into data parsing, extrapolation and recursion... without knowing what any of those terms.

2 ½ hrs later. still nothing... assuming he was confused, I set up a 'quick' call...near 3 hrs later I think he got that it was only meant so I could see if/where he didnt understand... not dive into building extensive data arch... hopefully.

So, we need some basic af PHP forms for some public-provided input into a mySQL db. I figured I'd have him look up mySQL variables/fields, teach him a bit about proper db/field setup and give him something to practice on his currently untouched linux container I just set up so he could have a static ipv4 and cli on our new block (yea... he's spoiled, but has no clue).

I asked him to list some traits of X that he thinks could be relevant. Then to essentially briefly explain the logic to deciding/returning the values/how to store in the db... essentially basic conditionals and for loops... which is also quite new to him.

I love databases; I know I'm not in the majority... I assumed he'd get a couple traits in his mind and exhaust himself breaking them down. I was wrong. He was/likely is in his sleep now, over complicating something that was just meant as a basic af.

Fyi, the company is currently weighted towards more autistics (him and myself included) than neurotypicals.

I know I was(still am) extremely abnormal, especially when it comes to things like data.

So, should I be concerned/have him focus elsewhere for a bit?... I dont want to have him burnout before he even gets to installing mySQL

Ye, so after studying for an eternity and doing some odd jobs here and there, all I can show for are following traits:

* Super knowledgeable in arm/Intel assembly language
* C-Veteran with knowledge of some sick and nasty C-hacks/tricks which would even sour the mood of your grandma
* Acquired disdain of any and all scripting languages (how dare you write something in one line for which I need a whole library for!)
* All-in-all low-level programmer type of guy (gimme those juicy registers to write into!)

After completing the mandatory part of my computer science studies, all I did was immerse myself into low-level stuff. Even started to hold lectures and all.

Now I'm at the cusp of being let free into the open market.
The thing is: I'm pretty sure that no company is really interested in my knowledge, as no one really writes assembly anymore.

Sure, embedded programming is still a thing, but even that is becoming increasingly more abstract, with God knows how many layers of software between the hardware and the dev, just to hide all the scary bits underneath.

So, are there people in here who're actually exposed to assembly or any hands-on hardware-programming?
Like, on a "which bit in which register/addr do I need to set" - kind of way.

And if so, what would you say someone like me should lookout for in a company to match my interest to theirs?
Or is it just a pipe dream, so I'd need to brace myself to a mundane software engineer career where I have to process a ticket at a time?

(Just to give a reference: even the most hardware-inclined companies I found "near" me are developing UIs with HTML5 to be used in some such environment ....)

Three key traits of software developers are laziness, impatience and arrogance.

Here's a task for the bored of you ;)

"Write a python script that prints out all numbers y from one to 10**30(including 10**30) that have two of these traits: [n**5=y, m**3=y, x**2=y] but not the other one; n and m are whole numbers."

Correct answer was about 103000
I can't seem to find the solution... Here's my (failed) try:

So... I went to Google's Applied CS with Android programme.
Had fun, some good people I met, finally there is a person I know who loves C/C++ as well and has similar traits to mine.
Other than that, I still hate Java dearly and idk how I got selected.
But... It. Was. Fun!!! 🤗🤗

I usually crib about how stupid people are and how I struggle to stay afloat.

Let's switch some gears now. A post about some good people, product, and processes.

You know what the common theme here is?

The goodness here cannot be measured. Your first interaction with them makes you feel so comfortable that you start feeling butterflies.

These people just keep on giving. They are selfless. They are pure. They actually care.

And when you think it's done, then they give you some more.

What blows me away is, they don't expect or accept anything in return. Absolutely nothing. Not even a simple thank you.

And they are like a wizard. They walk into your life when you least expect them but need them the most. And when the task is done, they'll be gone before you even know.

No lingering, no drama, no bullshit. Just pure goodness.

Like my ex-lead in current company, I have a very senior guy in neighbouring team (for which they were gonna hire me initially), who also happened to interview me, is a gem.

He takes care of me like his own younger brother. Supports me and always answers my queries no matter how occupied he is.

And same is with good products and processes. They feel effortless. So smooth and add exceptional value to your existence. They give rise to wonderful companies.

You'd never experience a single negative aspect about them. No matter how much you try, things will just keep getting better until they don't need to.

And then they'll be long gone. Never to be seen again and never to be forgotten.

You cherish them only in your memory and wish they lasted longer. But they didn't because the purpose was served.

Such people and experiences inspire me. They push me to become a better human.

No matter how the world is or how it treats me, I must always live with high values and be a better version of past self.

The other evening, I was conversing with my mother where we spoke about some family friends who are insanely wealthy but humble and kind.

Mom and I mutually agreed that they don't have such good traits because they are wealthy, but they are wealthy because they live with humility, kindness, and pure intentions.

World is surely a beautiful place because of such people and I aspire to be one. May lord guide me well :)

The traits that compile to form a programmer

-Not good at naming things

-People started asking for you to fix electronics regardless of what you tell them You’re actually studying/good at

-Procrastination through the roof

-Lives off of Coffee, POP, Energy drinks, or what ever source of caffeine.

After doing more and more c/c++ I've started exhibiting traits of Jeho... Cplusplus' witness..

Two evolutionary traits that would've made us decent animals if we never got smart:
1. Running. On the African continent, there are hardly any animals that can outrun humans. Yes, cheetahs and whatnot are faster in a short run, but humans sweat and can cool down their bodies efficiently in a long run. Human can chase down pretty much anything. You can't run away from a human.
2. Throwing. Humans are the best throwers in the animal kingdom. Monkeys can throw too, but because of their long arms, they lose balance and can throw objects nowhere near as far and strong as humans.

!dev (maybe slightly)

I went to a CV Workshop organized by my first school. The presenter was the slightly-arrogant/know-it-all/cool type of guy who's a recruiter and also has his own company he runs. The presentation was OK, even though it took longer than announced. However, there were some things that bugged me. He expects everyone somehow to be extraordinary. Granted he works as a recruiter and his clients would like only the cream of the top, but some of the examples he gave from his personal experience, he seemed to give more gravity on other traits of the candidates than their achievements and qualifications (e.g. rejecting a candidate because she had posted a photo of her clubbing on Facebook). Also, somehow he judges candidates based on their parents profession. Lucky me that I fall into the category he dislikes. Now the fun part (sorry for the long post):

Next week there's a career day. I sent my CV as soon as I got the mail and then I also phoned the person in charge (as per the instructions). Yesterday on the workshop it was said we should resend our CVs by tomorrow on another mail? No problem you may think, but that said recruiter will take a look on them and that means I will have to rework mine just to make sure it is to his liking. I'm no fan of writing mission statements, nor trying to guess what my qualities (aka soft skills) are because what I think I am doesn't mean I actually am.

So now, I'm in a dilemma. Just send the CV as is or get a mental breakdown just so to please that person?
Thanks everyone for your patience and time, I just wanted to pump some steam out me...

typeof rant === "Encouragement"

Never let your self down, try to be your own const in life that know his scope and traits well enough to construct a peacefull life without any uncatched exceptions. Also try to return something to the public, keeping your magic pointers to your private makes it hard to review your glorious source of thoughts. And if it is getting hard try to REST a bit and git some timeout.

😉

I’m one of those who learned in adulthood. I had lost track of my life and tried to find something to grasp on to. I found inspiration from two friends I have. One who’s been a very gifted software engineer since his early years, and the other who one day unexpectedly turned to university and computer science and started a good work life right away after the studies. After failing miserably at my previous attempt at university I decided to jump ship and give CS a try. It was the best decision of my life. To my surprise programming very much matched many of my personality traits and how I think and make desicions in games and everyday life. After my first few lectures It all came very intuitively to me. Then thruout most of my education (and this is one of my less ”grown up” thoughts) it felt as though I could as well have been a student at Hogwarts and my professors were witches and wizards. Anything was possible and each day we learned new tricks to create the unimaginable. That aside, I now work as a software engineer, but I feel as though the list of things left to learn is endless. I don’t think I’ll ever stop learning.

what are the key traits of a good dev?

!rant but story

Didn't participate in this week rant since the topic is not very relatable to me.

I rarely get truly inspired. There are people I envy. There are things I like. There are moments I go, oh awesome. That's about it.

I doubt myself that I have little bits of narcissist and sociopath traits. Maybe I am. 🤔

For some reason I keep over engineering stuff to the point I spend 2 hours thinking the best way to do something. I'm making the backend for a project of mine and I wanted somewhat decent error handling and useful error responses. I won't go into detail here but let's say that in any other (oo) language it would be a no-brainer to do this with OOP inheritance, but Rust does OOP by composition (and there's no way to upcast traits and downcasting is hard). I ended up wasting so much time thinking of how to do something generic enough, easily extendable and that doesn't involve any boilerplate or repeated code with no success. What I didn't realize is that my API will not be public (in the sense that the API is not the service I offer), I'm the only one who needs to figure out why I got a 400 or a 403. There's no need to return a response stating exactly which field had a wrong value or exactly what resource had it's access denied to the user. I can just look at the error code, my documentation and the request I made to infer what caused the error. If that does not work I can always take a quick look at the source code of the server to see what went wrong. So In short I ended up thrashing all the refactoring I had done and stayed with my current solution for error-handling. I have found a few places that could use some improvement, but it's nothing compared to the whole revamp I was doing of the whole thing.

This is not the first time I over engineer stuff (and probably won't be the last). I think I do it in order to be future-proof. I make my code generic enough so in case any requirements change in the future I don't have to rewrite everything, but that adds no real value to my stuff since I'm always working solo, the projects aren't super big and a rewrite wouldn't take too long. In the end I just end up wasting time, sanity and keystrokes on stuff that will just slow down my development speed further down the road without generating any benefits.

Why am I like this? Oh well, I'm just glad I figured out this wasn't necessary before putting many hours of work into it.

the irony appears to be that JavaScript is more consistent than rust

so let's say you want to create some enums to represent some potential values in a REST JSON payload

well you can implement Display trait but that won't determine the JSON output
you can make a as_str() method and that doesn't even make sense frankly, I guess it's not even a trait even though it's everywhere in the std library? (traits being rust's version of interfaces, so you'd think they should be consistent)

I have a halfway urge to say rust was a beloved language but then the foundations' drama made everyone escape the ship, leaving behind a mess

well evidently the answer is you use the stupid annotations:
enum Lang {
#[serde(rename = "en-US")]
EnUS,
}
well then this only works in serialization with serde. way to go.

how about if I have some JSON data that starts with numbers? I have an interval field in the REST that expects things like 1m, 15m denoting time scale
well no deal
because rust doesn't want enums starting with numbers

and here I thought rust was superior with its static typing. but I am having to rename things all the way down and nothing is consistent. this would be so trivial in JavaScript. and there's only one toString() method! and no interfaces people say you should use while nobody uses them!

!dev

Every day that goes by, I learn something about myself.

In my mind I have an explanation of who I am, which I usually think is fixed.

Presumed flaws, presumed virtues presumed traits.

All forming an alibi of my presumed self.

You know, a good person who is a bit of an asshole, an advocate for the underdog but who rarely does anything brave.

And also, a 100% straight guy.

But then you go to the movies to see Aladdin, and an hour into the movie for like 30 seconds Will Smith shows up like a trap, wearing make up and shit and you think to yourself "I could totally fuck this dude on his fucking face".

What a curve ball.

The code of conduct is a good thing. It doesn't persecute cis white men. All it does is tell you not to harass people on the basis of traits they cannot control. You say you only care about code quality and nothing else? There's a whole untapped market of talent from women and lgbtq+ people who stay the fuck away because of toxic communities. When you call people faggot it makes them not want to contribute to your codebase.
Linus stepped down of his own volition to try to become a more constructive voice. Heaven forbid the assholes have some introspection.

Hate it because it's vague. Hate it because it means anyone can be banned without evidence. Don't hate it because the assholes are finally being called on their bullshit.

Máni is an open source general purpose programming language. It is built on top of Java, and has some of the traits of JavaScript whilst also being unique.

We would love some people to join the development team and help us out with some issues.

I'm going to confess: I am the type of developer that creates the ExcruciatinglyLongAndSpecificClassNameObject with the UtterlyDetailedExplanationMethod. It's just a thing I keep doing, despite voiced frustrations from people I've worked with. It just feels right in the mindset of self-documenting code

And while I acknowledge this isn't a flawless process, I see no other way around without losing information. I've tried alternatives, but everything feels like trading one issue for another:

- Abbreviations work as long as they are well known (XML, HTML, ...). As soon as you add your own (even if they make sense in the business context) you can bet your ass someone is going to have no idea what you're talking about. Even remembering your own shit is difficult after X months.

- Removing redundant naming seems fine until it isn't redundant anymore (like when a feature with similar traits gets added). and you can bet your ass no-one is going to refactor the existing part to specify how it differs from the newly added stuff.

- Moving details to namespaces is IMO just moving the problem and pretending it doesn't exist. Also have had folks that just auto-include namespaces in VS without looking if they need the class from namespaceA or namespaceB and then proceed to complain why it doesn't compile.

So, since I am out of ideas, I'd like to ask you folks: Is it possible to reduce class/method name lengths without losing information? Or is self-documenting code just an ideal I'm trying too hard to achieve? Or are long names not a problem at all? I'm looking forward to your answers.

A bit late.. and not much about how to learn to code..but more of a figuring out if the kid has a right mind set to do so..

If the kid is not the type to question everything, not resourceful, not a logical/critical thinker, gives up easily and especially if not interested in how things work then being a dev is most probably not for them.. they can still persue coding, but it will end badly..

From my experience, people who have a better education than me, but lack those skills turned out to be a crappy dev.. not interested in the best tool to complete the tasks, just making 'something', adding more shit to the already shitty stack.. and being happy with that.. which of course is not the best way to do things around here..or in life!!

Soo.. if the kid shows all that and most importantly shows interest in learning to code.. throw him the java ultimate edition book and see what happens.. joke!

There are plenty of apps thath can get you started (tried mimo, but being devs yourself it's probably not so hard to check some out and weed out the bad ones) that explain simple logic and syntax.. there is w3schools that explains basics quite well and lets you tinker online with js and python..
so maybe show them these and see what happens.. If it will pick their interest, they will soon start to ask the right questions.. and you can go from there..

If the kids are not the 'evil spawns' of already dev parents or don't have crazy dev aunties and uncles, then they will have to work things out themselves or ask friends... or seek help online (the resourceful part comes here).. so google or any flavour of search engines is their friend..

Just hope they don't venture to stack overflow too soon or they will want to kill themselves /* a little joke, but also a bit true.. */

Anyhow, if the kid is exhibiting 'dev traits' it is not even a question how to introduce it to the coding.. they will find a way.. if not, do not force them to learn coding "because it's in and makes you a lot of moneyz"..
As with other things in life, do not force kids to do anything that you think will be best for them.. Point them in direction, show them how it might be fun and usefull, a little nudge in the right direction.. but do not force.. ever!!!

And also another thing to consider.. most of the documentation and code is written in english.. If they are not proficient, they will have a hard time learning, checking docs, finding answers.. so make sure they learn english first!!
Not just for coding, knowing english will help them in life in general. So maaaaybe force them to learn this a bit..

One day my husband came to me and asked me how he can learn.. and if it's too late for him to learn coding.. that he found some app and if I can take a look and tell him what I think, if it is an ok app to learn..
I was both flattered and stumped at the same time..
Explained to him that in my view, he is a bit old to start now, at least to be competitive on the market and to do this for a living, but if it interests him for som personal projects, why not.. you're never too old to start learning and finding a new hobby..

Anyhow, I've pointed out to him that he will have to better his english in order to be able to find the answers to questions and potential problems.. and that I'm happy to help where and when I can, but most of the job will be on him.

So yeah, showed him some tutorials, explained things a bit.. he soon lost interest after a week and was mindblown how I can do this every day..

And I think this is really how you should introduce coding to kids.. show them some easy tutorials, explain simple logic to them.. see how they react.. if they pick it up easily, show them something more advanced.. if they lose interest, let them be.

To sum up:
- check first if they really want to learn this or this is something they're forced to do (if latter everything you say is a waste of everybodys time)
- english is important
- asking questions (& questioning the code) is mandatory so don't be afraid to ask for help
- admitting not knowing something is the first step to learning
- learn to 'google' & weed out the crap
- documentation is your friend
- comments & docs sometimes lie, so use the force (go check the source)
- once you learn the basics its just a matter of language flavour..adjust some logic here, some sintax there..
- if you're stuck with a problem, try to see it from a different angle
- debugging is part of coder life, learn to 'love' it

1. Say something about autistic traits in front of your boss. Mention many developers benefit from those traits in their engineering work.
2. Boss rejects this audibly saying he is not in fact autistic.
3. Pretend to ignore social cues when interacting near boss. Such as interrupting conversations impolitely. Boss ignores this and doesn't mention this.
4. Later hear boss saying he might have some autistic traits that helps him in his work (he is software developer and electrical engineer, and is very good at this).
5. Profit from being an asshole or autistic? Am I ignoring cues because I just don't give a fuck anymore?

Learning how to break a result into the steps necessary to produce it, along with the broader concept of abstraction in computer science has allowed me to apply this thinking to my personal experience. I've traced personality traits and behaviors to specific events from my childhood, and can finally relax knowing that understanding computers has given me all the linguistic tools I need to talk to myself, which traditionally has been impossible. I no longer feel trapped in a terrifyingly imaginative mind.

I can't name just the one annoying coworker, because I've never had this one person I really, really couldn't stand being around. But there are plenty of coworkers that have crossed my path over the years with features that have slowly driven me towards madness.

Like the team leader with psychopathic traits and a brown nose stomping downwards and pleasing upwards.

Like the one fellow who set variable values multiple times to really, really be certain it was set.

Like the girl who sat next to me every now and then, and always started humming and singing only when she sat next to me. Always just loud enough for me to hear.

The dickhead coworkers that has been bullying me, excluding me, neglecting me over the years.

The managers who apparently never learned managing nor people skills.

Every jackass that thought it was a good idea to come stand next to me so they could have a nice conversation on the phone without being disturbed. Well, you disturbed me!

The manager who was whistling and singing so loud from his office that I had to get a Bose QuietComfort headset to get him out of my head.

Every fucking one contributing to the dinosaurism haunting the office.

Rust's Fn traits feel weird. The argument tuple is a generic parameter, but the return type is an associated type, even though Rust is supposed to use Hindley-Milner type inference, so inferring through return type should always fail if this were a regular trait.

Then, this would mean that blanket implementations for Fn(T) and Fn(T, U) should conflict because AnyTrait<(T)> and AnyTrait<(T, U)> aren't mutually exclusive. I tried, they work just fine.

There's some weird and I suspect unnecessary special case magic here, and I'd like to uncover it.

What do you guys think of php's traits?

For those that don't know, traits provide copy/paste discount inheritance functionality. You can include common methods or properties. For example, I use the TimestampableEntity trait to include createdAt, id and updatedAt fields to my entities. They're really useful for simple stuff. You can include multiple traits in one class and it will error on clashing methods/properties

Rust, I demand you give me dyn trait support for async traits now.

Was there a thread "php traits are pure evil"? If no let this will be one

Who can explain better traits and method in php?

I have a platform idea, I need feedback

Problem statement: it’s hard to find researchers of specific area, which discourages students to even start looking for research opportunities. The reason for that is because people often look into their own academic circle, and the resource available is simply not enough.

Solution: by scraping Google scholar, generate detailed tag of sub areas for each professors, make a search system for that which will display the most important works of a researcher and what they are working on recently. If possible, invite the researchers to use the platform to add tags of traits they are looking for in students.

I have quite polarized feedback right now, one is the subarea tagging is really useful and academic circle is a problem, other is this is completely useless.

Please let me know what you think.

I can't tell if I didn't understand an important detail about Rust traits or the system is badly underdesigned, but I keep bumping into situations where the most general correct implementation of an std trait on a container clashes with one of the std implementations, and I would need a very obvious negative statement to make them mutually exclusive (for example that T in MyPtr<T> can never implement Borrow<MyPtr<T>>)

I've been trying to define a trait `Inherits<T>`, a trait `Extends{ type Parent }` and an arbitrary amount of scaffolding around it such that

- the scaffolding for a given type only has to acknowledge that type, its parent and the types of which it is a parent
- `T: Inherits<U>` if a chain of `Extends` leads from `T` to `U`

I suspect that this is impossible, but I'd seen Rust traits bent to do crazier things, so if you know of such a system or can come up with a way to implement it despite the orphan rules, I'd be over the moon.

It seems I, have been having few borderline personality traits. Apparently borderlines have different sensitivity to physical pain. Interesting.

Is this a justified code review comment or a bully?

Code reviews are weakness of this industry which has the potential to attract bullies. Abuse of the comment box in a pull request and bombarding the employee with hundreds of comments can cause stress, frustration, burnout and finally resignation and costs of fulfillment for the organization. While companies should find and stop bullying in the work place, what kind of code review comment is considered a bully and why? Any of below traits can mean you are dealing with a bully:

1. Claims the code needs to be changed but doesn't say how. So no matter how many times you change your code, he can repeat the same comment: "Your code is still bad due to blah blah and it needs to be changed".

2. Provides how the code should be changed, but the change doesn't add up to quality, security, performance, readability, etc. i.e. "Why did you use a for loop here? Use a while loop instead". Or "Why did you write it using three classes A, B and C? Instead write it using 4 classes D, E, F and G which does blah blah". In the later case, not following the review comment, you won't get approval. Following the comment means you need to rewrite your whole code. After which, you might again receive more comments to change other parts of your code!

3. Claims the requested change is due to standards but claimed standard does exist anywhere. Internet, company wiki, university course books, anywhere. In more severe cases of psychopathy, the bullying person refers you to a link which hours later turned out to be written by himself! Have fun describing what has happened to your manager or team leader... .

4. Asks the code to be changed in a way that supposedly is closer to standard or of better quality, security, performance, etc. But the proposed way will not work and is the main reason you didn't do that in the first place. So you start arguing forever in the comment box over why his method won't work!

If you cannot see any of the above traits, then keep calm, take a breath, fix your code. Otherwise you might be victim of a bully.