erogenouswarzone @ erogenouswarzone @lemmy.ml

Posts

1

Comments

253

Joined

2 yr. ago

How about a wireless lapdock for my desktop, so I can have the processing power in mobile form.

I feel like there was a Built to Spill song about that.

Thanks man

I hope you don't. And I'm sorry.

I lost my best friend in February. It fucking sucks.

He was a big partier. Once he hit his late 30s he ballooned to probably over 300. He took a nap one day and had a heart attack in his little attic room of his friend's house, where he had lived for 10 years. Our big friend group from back in the day is wondering who will go next.

What about sublemes

In my experience, there's two ends of the developer spectrum.

At one end is uptight. They have all their shit on lockdown and the confidence that comes with that.

The other end is creative. They are developers because they enjoy creating, and development is a rare high-paying but creative outlet. They stumble through everything and get bored with reading too much documentation.

I have seen many cases of both of these, and another, underlying metric is their perception of their own intelligence.

It's unfortunate, but a lot of them grew up in an environment where they were the smartest person in the room and were rarely challenged. Now, being in an environment with many other smart people, they only feel smart by making others feel less than.

They purposely show off their knowledge and when you give an idea they shit on it and make you feel stupid.

There's also this thing where if you know a system really well, it's hard to imagine someone not having the knowledge you have. This is just how memory works because our brains abstract things away and then we can't recognize when others don't have that abstraction yet.

This is all normal. Humanity has a lot of work to do to change this, but it's embedded into how everything works, so it's not going to happen in our lifetime. You can change you, but you can't change anything else.

With that being said, here are some things I have learned, being from a similar background as you:

1. Recognize that you are smart or you wouldn't be there.
2. Accept that others will make you feel stupid. The best response is to act like it doesn't phase you.
3. Don't make others feel stupid if you can help it.
4. Be enthusiastic. Any shortcomings you may have, will be forgiven if you show up with a big smile on your face.
5. Talk to your managers. Ask them what would make you better at your job, and ruthlessly pursue bettering yourself. This will give you a lot of confidence.
6. You will lose touch with your old party friends. They will die young, and you will feel sad. When you do get a chance to catch up, talk to them a lot and consider journaling it. This will help a lot when you lose them.
7. You will feel guilty because you are doing so much better than them. Accept it and move on and try not to brag about your new life.
8. You will feel out of place because your new friends don't have the same background as you. Accept it and move on. Nobody else is worried about it.
9. Your new friends will probably not be as interesting as your old friends, and you will feel yourself becoming less interesting. This is the price we pay for our new life. If you want to stay interesting find a way to be in touch with other creative people: musicians, teachers, English majors.

It eventually gets absorbed by the pasta and makes it creamier. Unless you have too much water.

Nooo. You need the perfect amount of water so it reabsorbs it's own juices. Succulent Cannibalism.

Microsoft has deprecated vbscript and it will not be shipped with future versions of windows.

Important Breakup Advice:

Make a list of everything you hated about being with them, focus on the bad feelings their behavior gave you.

When you get sad about not being with them refer to the list. It works surprisingly well.

I think it's very cool. Let Reddit have them. We're doing pretty good over here so far. The last thing we need is to be overrun by normies again.

The place I work decided to name all tables in all caps. So now every day I have to decide if I want to be consistent or I want to have an easy life.

Talk to a therapist. Not just you, everyone.

We all have trauma, talking about it can help you come to peace with it. Then it won't be this cringe thing (or whatever negative emotion it invokes) in your thought pattern.

Ever since that article about VSCode collecting data yesterday, I don't think I'm going to be learning anything new from Microsoft.

AutoHotKey AHK for short. Allows automation of nearly anything in Windows, and is better than most alternatives. The downside is it's VBScript, which I believe is going he way of the dodo, and it has quite a few gotchyas.

However, on day one you can start assigning keys and combos to do common tasks.

Don't like Caps Lock? Reassign it to open Chrome. Hate that you can't lock the screen with your left hand? Make Win+S a command that locks the screen.

It's free, has a huge community, and is truly amazing.

I've heard it's as addictive as sugar. Be careful.

Even using absolute best prackies, developers are gonna find a bunch of stuff to complain about.

As a person who victimizes coworkers like this, I apologize. Thank you for pointing it out, and I will stop doing it.

No offense, but I know how to read a stack trace, and yes locate a familiar file - if you're lucky enough to have one listed therein.

My point is, there is no excuse for them being so terrible except that they've always been that way.

The important information should be brief and at the top. This is design 101. The same ideas that have driven newspaper articles and websites for as long as the two have been a thing.

You put the important stuff in big letters at the top, and the rest, if you need it, is beneath the fold.

Edit: just to drive the point home: I'm sure it's not the packages I've downloaded that are causing the error, I am positive it is my code, so show me where my code had a mistake first. Then you can show me the horrible "wall of text" that is the stack trace so I can understand it better later, but 99% of the time, just seeing the line that caused the error is enough to know what the problem is.