deeteecee

The signage is not clear and also, you're directly faced in an environment that's not friendly so yeah, it will fail.

I don't see that we're gonna lose that satisfaction you describe anytime soon. But if everything I typed is via prompt engineering, yeah I'll be a little sad.

backed me up and provided engineering support. raised my salary regularly, knowing i was a valuable engineer.

lol I feel that man's rage. I've shouted the same lines while trying out a new tool

no but ive ran into occasional issues where it's "plugged in" but not charging. I just pull it out and plug it back in to make sure it's on.

It sounds like you're just saying it's boring when an adequate library/framework is available. But I've never heard of such a library/framework that makes it THAT easy.

Either the software you're working on is simple or the projects are too small and not complex enough for you. Has nothing to do with Python.

since you mentioned your open mind having difficulty, it sounds like you need to to improve the ability to tackle these issues more methodically and slowly plan out a strategy of attack instead of just trying things.

nice, you even brought my 500+ ping lag back into the mix.

not wrong/right but I was watching a video where monkeys were eating bananas. And then I tried it and now I've stuck to it. I've always had issues opening bananas so for me, that's the right way.

I mean, if you eat healthy, your poop comes out pretty clean is my understanding. But we Americans certainly can't make that argument :)

I can work much faster on Python than Java and I know both pretty well. I'm not aiming for scalability in the initial stages of my imaginary startup.

That being said, it wouldn't be the worst thing for me to start with Java

He wasn't saying just because you have GitHub stars you should get paid. He's encouraging open source developers to be proud of their work and not be shy about setting up a method for getting paid.

I think with different OS's you're still gonna have some challenges but the fact is you still get better consistency, especially if you're on a Linux machine. I use the Mac and I have minor issues with the network, performance, and having to manually clean up my docker storage from time to time but I'll take that anytime over wondering why I can't install something or reproduce an issue in another env.

I don't see anything hype about it. You might just be frustrated with more of the minor issues.

I wouldn't consider this a failure. Delaying a project by not communicating this would be a failure.

there is no correct answer but someone at the senior level would probably be able to explain the same kind of problem in more depth.

im not an expert but i think you can just do the first-order dependencies on requirements.txt and then do a pip freeze with constraints.txt and do `pip install -r requirements.txt -c constraints.txt`. that'll make you both happy.

Before constraints.txt came into play, I would've done what you said with pip freeze. With only first-order dependencies, that sounds more likely to break at some point due to the other potential version changes. I think your colleague needs to explain why things are breaking in his case.

i didn't learn anything here but i was amused :)

Here's a few pain points I had:

* Virtual VM's don't solve my problem everytime. There's software that still requires x86 and a VM isn't going to solve that problem in a few cases. I wish I could get into more details here but I'm kind of a noob in this realm. (TLDR: I need to use something called UAExpert and to resolve this, I have both a separate Linux machine and Windows machine in case I need it)

* Have to install homebrew and an x864 version of homebrew to run the right software. Homebrew does not document this so this solution was based off stack overflow posts.

* While docker states that it supports multiple architectures, I don't find that to be fully true. For our codebase, I need to push up x86 docker images but accidentally pushed up arm64 ones instead. There's a solution for it but it's definitely not an out-of-the-box solution at the moment.

Overall, still pretty happy with it. My older macbook pro had gotten sluggish so the tradeoff for me was worth it.

I stopped playing because I spent most of my time running around the map while being stuck with certain problems. If there was a speed-up button then I would've kept trying.

For what it's worth, all your bullet points describe a pretty normal and healthy person to me.

a lot of of these patterns are very paradoxical.

I think this means that you're a balanced person but maybe your maybe your anxiety energy is a bit strong.

No matter how hard I try I can't do them any faster

Maybe stick to slow instead of trying both slow + fast. You can also think about why fast didn't work.

when I get some free time I get anxious about having to use this time wisely

This last one hits pretty close to home for me as a person and I really wish I knew how to set up my free time better :)

For kubernetes, we prefer GCP but have to also support Azure because Microsoft is also our business partner.

They're not arguing that testing or staging environments are bad, they're just saying their organization couldn't manage to get them working.

That is exactly what I got from reading this article. Their staging process was poorly set up and they simply abandoned ship. Additionally, I was getting poor software culture vibes.

How did your hiring managers respond? That sounds terrible and racist in itself.

FWIW I have the active, recent interview and work experience and even after preparation and attempts for an entire year, I did not find a new job.

Don't be afraid to ask questions. Also, avoid scope creep if you can. Good luck!

that was beautiful. thanks for sharing

I think it's not so much a problem of fast talker rather than familiarity. If you speak to each one of them individually, that's one way to improve.

They might be jumping in faster because their level of familiarity is strong already.

you could just put them in a repo

i recently learned their word for a video going viral which is the verb バズる ("bazuru" aka buzz)

id recommend focusing on documentation that goes through much more complex layers than fussing over this.

And he's also misreading what simple means.