8 hours of meetings and 10 minutes of writing code.
Asklemmy
A loosely moderated place to ask open-ended questions
Search asklemmy π
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
Nailed it!
When I was an associate level all I did was grind out tickets and write code. Now I run from meeting to meeting as a senior.
Thatβs surprising accurate for many developers.
It involves a lot of tall girls in thigh high socks, sometimes they wear cat ears too. And they do a lot of typing on extra clackity keyboards.
College recruiters be like ^
Ctrl+C
Ctrl+V
You just revealed yourself as a programmer.
That sounds ridiculous. It 2024, I'm pretty sure programmers just use voice input and say the ones and zeros instead of sitting there and doing all that typing. Still not sure why they have to wear black hoodies though.
There's a dress code. Very strictly enforced
Yes, and under the hoodies there are t-shirts that were given out at conferences. That or memes. Strict.
You learn a special type of Spanish and somehow you make MS Word come out
This one is the closest, IMO!
Is it common knowledge that programmers write code in different "languages" (e.g. Java and C++)?
Reads code, spends too much time figuring out what it does and why the compiler is complaining about it, find out who wrote it, open drawer of voodoo dolls, rummage through them and pull out the relevant doll and stick another pin into it. A faint scream echoes through the cubicle farm. Place voodoo doll back in the drawer, close drawer, leave for lunch
Itβs like building the NY subway systemβyouβre constantly adding on new bypasses and trying to maintenance old tunnels in order to account for new features/population. It ultimately ends up working most of the time and the daily commuters get to move from Point A to Point B with minimal interruption, but if you viewed the subway as a whole itβs a cobbled mess with lots of redundancy. Some of the architects who are currently around donβt even know where the oldest tunnels go, or why theyβre there.
Wanted to give a take on it that didnβt focus on the obvious βlanguageβ aspect. I could be 100% wrong on thisβIβm sort of basing it off of comments Iβve seen here or there. I know very few folks who work in tech and I work in healthcare.
Honestly that's more like network engineering than programming, but you're surprisingly accurate.
This is an accurate representation of tech debt.
-
Type some algebraic equations into a text file.
-
Run it through something called a "compiler"
-
Suddenly everyone knows what the fucking weather is.
I don't know if Lemmy is the best place to ask, lol
I think its like trying to get a toddler to accomplish a task and it keeps technically doing what you said but in an annoying and counterproductive way you didnt even think of yet and you have to just become insanely specific about what you want the toddler to do and when and in what order with what timing
That's actually really accurate when first learning to program. Eventually you figure out how to think like a toddler.
Given that I stole this from a programming community, it shouldn't be too far off from true.
(Caveat lector: I'm not in the IT industry but I'm often messing with bash scripts and decompiled python code.)
Well idk about all programming, but I imagine hackers go through at least one keyboard a month and suffer serious finger strain injuries from typing so fast and furious.
I'm a hacker. You don't even want to know what my monthly budget for balaclavas and fingerless gloves is.
Swinging between feeling like you're a computer god, and then feeling like you're horrible at your job.
Playing with imaginary Legos to put together a rickety tower.
Edit: though on reflection, a systems approach to nursing the acutely ill is exactly the same but we're maintaining "God's" legacy code while we try to keep someone with kidney, heart, and lung problems functioning with judicious application of fluid management, drugs, and dialysis.
Maybe what we do is closer to Jenga.
I would imagine it is as follows:
-
Come up with ideas or goal to accomplish /be given said goal
-
spend large amount of time looking at existing code or prior implementation of your stated goal.
-
attempt to write or import some code tailored to your specific needs
-
test and identify problem areas
-
find everything fails spectacularly and start over +/- tears.
-
repeat until successful or dead
They said people outside the tech industry
A laughably small team is expected to do tasks that take triple the team size to do properly, and then the team gets endlessly shit on for Facebook looking different now for unrelated reasons while getting zero recognition for somehow finding a way to get some massive project done on an absurd timeline with no additional resources.
I have been in power plants for many years now. Nobody notices us until we fuck up, and then nobody ever forgets. For example, Three Mile Island.
I assume itβs looking for that one space that should be a semi-colon in a sea of garbled letters.
This is 100% accurate.
Imagine a poorly lit room. The smell of coffee permeates every inch while the Baba is You soundtrack is played on repeat. Five to fifty monkeys sit in desks and attempt to bind whatever devils are necessary to invoke the magic their leader demands. sixty three percent of their effort is actually just browsing social media and posting memes in niche online communities, but they still manage to get stuff done.
Judging by the amount of their nonsense posted on Lemmy, I imagine programmers sitting around all day creating memes about how hard their job is.
Seriously, this is the most Lemmy-ish post I have ever seen. "I see there are people not in programming discussing non-programming topics...what question can I ask to steer the question back to programming?"
You have super cool sunglasses and a chair where a needle goes in your brain... right?...
I figure itβs like what I used to do in grade school to make the turtle draw shapes in Logowriter, on an Apple IIe.
And you say you're not a programmer π
I'm pretty sure most of these comments are written by programmers π€£ reciting CSI stuff...
When things get really tough, two of you will double up on the same keyboard.
1 in 6 have multiple personalities and substance abuse daemons.
Your bosses ride little skateboards everywhere, when they're not busy programming animated singing viruses.
The FBI watches you code, but has no idea what they're looking at.
A significant fraction of you can type with your feet, proficiently.
I don't think about programming at all, no offense.
You guys talk to computers in the language of computers. You are trying to get the computer to do something you want. However the computer doesn't help you out, you have to tell it explicitly what to do down to the tinyist detail or it won't work and you will be sad.
To the outside observer this looks like typing gibberish and copying in chunks of more gibberish. With occasional swearing.
How'd I do? (I know very little about programming and computers, I've worked manual labor for something like 20 years.)
Playing ping pong in an office that looks like a spaceship, while chat GPT writes code for you. π Just kidding! I assume it is lots of problem solving and work around to make some feature your leadership put in the roadmap.