Backend colleague : the API is online. It's tested and working, you can start the dev.

Me trying to manually call the API with all the fields pre validated : "error : invalid fields"

EVERY. FUCKING. TIME !

To all the backend developers : we are NOT your personal testers, and we are NOT supposed to clean your mess because you're too lazy to FUCKING TEST THE HAPPY PATH!!!

Thank you for your consideration.

Use this as a template to send rejection letter to your recruiter as a revenge.

"Dear Recruiter,

Thank you for considering me for the software engineering position at your company. After careful consideration, I regret to inform you that I am unable to accept your offer.

As a highly qualified and skilled software engineer, I am confident that I could bring a great deal of value to your organization. However, after reading the job description and learning more about your company, I have come to the realization that I am simply too good for the position. I have no interest in joining a team where my talents and abilities would be underutilized and unappreciated.

Furthermore, I am a bit concerned about the working environment at your company. I have heard rumors that the office is dingy, the cafeteria food is subpar, and the company culture is lacking. I am a true perfectionist, and I refuse to settle for anything less than the best.

In conclusion, I must decline your offer. I wish you and your company the best of luck in finding a candidate who is worthy of the position.

Sincerely,
[Your Name]"

Head hunting interview:

Q: Are your front end dev?
A: Yup, I'm website's frontend developer.
Q: Are you good at AngularJS?
A: No, I'm not. I only know Reactjs, and Ember.
Q: How about backend, you said you know Rail?
A: Yes, maybe for 3 month experience.

Q: So we need Angular guy, but it seem that you are BAD at Angular. Can you JOIN our next interview?
A: Sorry. I already told you that I don't care about Angular. Isn't it totally different with BAD at Angular? Thank for your consideration. I'm out.

Is there any double standard such as without AngularJS you will be considered that you are terrible at AngularJS?

Opinions

Hello, I’m considering building a web framework.

My ideal features would be:
Customizable authentication system(considering using a jwt lib)
Embedded DB(bolt db)
ORM( writing my own)
REST api to DB (via code generator)
Code generator(generation of models and views via cli)
GUI to db(some admin dashboard)
CORS(web service right?)

Why?
Ease of development
Fast prototyping of small-medium web services.
Fun.

My question is, do i have to many things on my platter? Should i narrow it down into less featured framework? What feature should I focus on? How should i benchmark it? Should i write tests for absolutely everything or just for exported methods? What should i take into consideration when developing ORM API, Auth API...

The language is Go

Thank you for your input