|
nvm then
|
![]() |
|
![]()
|
# ¿ Apr 1, 2023 01:58 |
|
i can't imagine what the code behind magic the gathering would be like. some of the cards are wildly specific like "gain 1 land if one of your other creatures is wearing a hat", and then suddenly the devs have to add a "has_hat" check on every card dating back 30 years
|
![]() |
|
oh cool well in that case i am the terrible programmer
|
![]() |
|
doesn’t take into account hemispheres tho
|
![]() |
|
Plorkyeran posted:i don't think i've ever seen an architectural diagram which was actually intended to convey information and not just convey the feeling of information, but i am willing to believe that they exist any time any kind of documentation breaks out a flow chart to try and explain how it works, my brain immediately shuts off and refuses to parse it at all. i don't know what kind of brain they are meant for but it aint mine
|
![]() |
|
i am only 11 months into my current job and in that time i've only had jr devs to work with and let me tell you, tiresome doesn't begin to describe it.
|
![]() |
|
it would be cool if they asked things more often lol
|
![]() |
|
to be clear i am not ragging on jr devs as people. those i work with are generally good people, easy to get along with, eager to learn, fun to hang with after work and go for drinks. doesn't mean that working with them can't be tiring. the kind of stuff i am talking about is cargo culting poo poo from stack overflow, submitting a PR to fix a bug that carelessly introduces 2 more, or a general lack of debugging skills in general, straight up ignoring details in the task description. granted some of those are things that do come with experience and are harder to teach, but a lot of what i deal with could be avoided by simply asking more questions beforehand. one thing i see a lot is that in order to fix a bug, they will apply a band aid solution to the symptom instead of trying to discover the actual source of the issue. it is tiring
|
![]() |
|
![]()
|
# ¿ Apr 1, 2023 01:58 |
|
rotor posted:i am so tired of having to explain basic poo poo like "how to set environment variables" to people or how to follow the most basic stack trace to figure out why something isn't working
|
![]() |