Ehhh.

Ehhh.

Both have their pro's and con's

I DEFINITELY have bands and records I listen to because I know I like 100% of what I will hear.

But since I also want unusual and strange music, I sometimes find bands where I like 1-3 songs only.

But I WANT those bands to make the songs I do not like. They are part of the proccess of making the things I like.

Cannot get good art if there is no tolerance for bad art

"There's nothing rarer than liking every song on an album" y'all are listening to the wrong albums

Burnout should... not be a thing that happens to you very often :s I hope you meant it more as "When I am busy" otherwise you may want to avoid to limit whatever gives you burnout if possible :s I hope I do not sound preachy. I say it because I am worrying because you seem nice, not because I want to dictate to you how to be, or pretend I know your life and situation. I DO like a mid day nap around 12 if I can get away with it. I will sleep under my desk if need be. But they are usually 30 min or so Means I am way more productive the last half of the day

Do any other autistics nap like...a lot?? On the weekends, I can easily nap 4+ hours and then still go to bed on time.

When I'm in burnout, I sometimes can nap repeatedly and then go to bed on-time.

I hope it all works out for you!

I hope you find answers to all your trouble and your workflow gets smoother!

I hope you find cheatsheets to help you and manage to write notes that helps you remember!

bitch java is so fucking annoying why does the S in String need to be capitalized but the i in int has to be in lowercase??? why do you need to import a whole ass module just to take an input from the user??? why are all the commands so fucking long and hard to remember??? JUST DIE

If the coding convention is not enforced with auto-formaters, it does not exist. If someone wants all the code to be written in exactly the same way every time... then get a machine to do that. Doing the same thing every time is what computers are good at. Set up a autoformater. If that is too much work. Then they have just said it is not very important, which means it is not very important. What IS very important is to make your code readable. Developers spend ~80% of their time READING code. So make THAT part easier. The code should fulfill its functional and performance requirements, after that, it should be made as easy to read as possible. It should take the reader from high abstraction overall idea and/or program flow, to more and more specific, so you can quickly get a overall idea and then deep dive only in the thing you are looking for right now. It should only use acronyms that it have defined in comments at the top of the file (If that is too much work... then do not use acronyms) If the code can only be understood with knowledge from outside the codebase, then that must be documented in a MD file. Nothing fancy, just write the thing down. If you cannot explain it in text, then make a diagram (I recomend draw.io). Easy, quick, no the specific style does not matter, just make it easy to read.

there's just a lot of "if everyone adopts my particularly tortured way of coding, everything will be great" going on, when 90% of the time this is extremely stilted and adds instead of reduces complexity. and you just don't have to do that. you can code normal style and nothing bad will happen

Ehhh.

Both have their pro's and con's

I DEFINITELY have bands and records I listen to because I know I like 100% of what I will hear.

But since I also want unusual and strange music, I sometimes find bands where I like 1-3 songs only.

But I WANT those bands to make the songs I do not like. They are part of the proccess of making the things I like.

Cannot get good art if there is no tolerance for bad art

"There's nothing rarer than liking every song on an album" y'all are listening to the wrong albums

This is sorta what I do

I spend less time on my tasks than most

Do not tell people about it. Spend the extra time reading documentation and the codebases. Taking screenshots. Making presentations.

And then I make my case that the company is shit in way X.

And when doubted, I have evidence. Nicely presented and alphabetically sorted.