My job was to organise the work between the workers, keep the business away from my subordinates, and only waste their time when they had the complete information being asked for the specific reason.
And if I wasn’t doing one of the things above, my job was to pick up the horrible things that no one else wanted/I had experience and domain knowledge in (eg : accessibility testing)
Have you considered writing your own projects that you have to hide from your employers, and be careful with whom you discuss, so as to avoid the legal complications of the company owning your work?
I just got a Jr dev job about 3 weeks ago and I haven’t written a single line of code. It’s all been meetings and other shit. I’m kind of ok with that. Lol
I think this is something a lot of people posting here don’t get. You can be a programmer, make apps or games in your spare time, set your own goals and be your own boss, and that’s great. Suddenly you get a “normal” job programming and you have you deal with customer requirements, business nonsense, and working as part of a team; that’s being a software engineer. One isn’t superior to the other, they are just different beasts.
Absolutely. There is very little programming involved in a normal job most of the year. I actually knew that before getting in. I have friends on the same team that have been there before me and they explained things beforehand. I have so many meetings and business stuff daily. We also reach out to users to help them fix issues on their machines, too.
I work on the City side of the development world. We’re always getting screamed at for taking 3 weeks to review a plan set by the same developers who want to meet with me every minute of every fucking day.
I’ve got 40 projects in my review queue and all of them are demanding a weekly meeting. When am I supposed to do the fucking reviews?
When you talk to your management and show them how overworked you are and ask for a helper. But don’t just say how much, show them in business lingo so they actually understand.
Fill out your calendar with the meetings and show management how you have no time for meaningful work because of meetings.
I’m on the Municipal side. City Council ain’t gonna raise taxes to hire more people.
I’ll get burned out and leave soon enough. The longest-serving person in the development department has been here just over a year, and we pay nearly double what other cities in the area do.
There’s a lot of us neurodivergent folks in tech because it suits our needs better than a lot of other fields, and a lot of us just love technology
We’re more prone to being LGBTQIA+ than neurotypical folks, scientifically documented
Makes sense tech would have more trans folks as a result, we pad the numbers a lil bit
This is of course a generalization and actual ND/LGBTQIA+ presence is going to vary based on job, location, how insufferable management is, etc, and not all NDs are LGBTQIA+ and vice versa.
I wasn’t saying the latter but that’s an interesting idea. Not the former per se- the cis heteronormative gender and sexuality binary is bullshit and only exists bc religion (capitalism… moar serfs in fields) and generations of fear. There’s tons of fluidity in earlier civilizations and more in nature.
I’d just like to hear some comments from all the downvoters. Odd thing to get so defensive about Lemmy
Margaret Elaine Hamilton (née Heafield; born August 17, 1936) is an American computer scientist, systems engineer, and business owner. She was director of the Software Engineering Division of the MIT Instrumentation Laboratory, which developed on-board flight software for NASA's Apollo program. She later founded two software companies—Higher Order Software in 1976 and Hamilton Technologies in 1986, both in Cambridge, Massachusetts.
Hamilton has published more than 130 papers, proceedings, and reports, about sixty projects, and six major programs. She invented the term "software engineering", stating "I began to use the term 'software engineering' to distinguish it from hardware and other kinds of engineering, yet treat each type of engineering as part of the overall systems engineering process."
On November 22, 2016, Hamilton received the Presidential Medal of Freedom from president Barack Obama for her work leading to the development of on-board flight software for NASA's Apollo Moon missions.
Huh, didn't know about her! She sounds like a badass lady!
People might be more familiar with this viral picture as well, if not the name.
“Margaret Hamilton shown in 1969 standing beside listings of the software developed by her and her team for the Apollo program’s Lunar Module and Command Module.”
My mom was a systems programmer who used assembly language and built a lot of the banking infrastructure!
Originally, programming was actually a woman dominated field because it was considered a subset of secretary work and “beneath men” (it wasn’t for a good reason).
If you watch the recent cummerbatch movie about Turing the eagle eyed observer will notice that nearly everyone who actually interacts with the computer software is a woman.
Not to turn this into a sociology discussion, but for anyone unaware: this is a fairly common pattern.
Women often pioneer fields like this, but as soon as it becomes seen as something “important” out “respectable” then suddenly it becomes male dominated.
The opposite also happens, where as society deems something as unimportant, a male dominated field will become female dominant - see teaching for an unfortunate example of a field that used to be highly paid and respected, and is now largely looked down on.
Sorry, don’t mean to go off on a tangent - it just bugs me and I think more people should be aware of it.
Beer brewing was originally a field dominated by women.
The presitege associated with a position can also change the expected gender. Women traditionally cooked meals at home but “Chefs” are predominately male, especially famous or celebrated Chefs.
You can google “women in computing” for more details, or check out en.wikipedia.org/wiki/Women_in_computing - it’s amazing how much women contributed to this field and how little known that appears to be. (I only learned about it a few years ago myself.)
But the gist is:
Early on (i.e. the 1940s and 50s), men thought the prestige and honor was in building the giant machines (which back then could fill a classroom or more). Actually programming them was considered easier, “just like following a recipe”, so women got jobs as “computers” who did this part. To quote that wikipedia article: Designing the hardware was “men’s work” and programming the software was “women’s work.”
Fast forward to the 1970s and people had started realizing that programming was actually hard, and so it was promoted as a field boys should get educated in, while girls were encouraged to instead become nurses and teachers and such.
using a computer traditionally was seen as a secretary job, so it was often dominated by women. its only as of post consumer computer events where a lot more males went into the field due to the large market it offers came in.
Something I’ve been for a while now is why this gender disparity is so strong in this specific area of engineering compared to all other engineering areas. People seem to claim it’s because of the “geek” stereotype, but that seems more like a symptom than a cause and I fail to see how it enforces this disparity, considering there’s nothing preventing a woman from being a geek too.
the actual reason? Nobody pushes women into the field of CS. Back in the 80s and 90s it was a similar thing, boys were fucking around with computers and software, not girls, it was considered to be a boys thing back then, and it still is now, because women are moving more frequently into higher expertise fields more often than not. CS while incredibly complicated, and difficult, is also just code monkey simulator at the end of the day. You could just write a PHD thesis on some mathematical shit and be as involved with CS while having been a mathematician instead lmao.
Nobody pushed me into this field, I followed it because I liked it. Same thing with kids messing around with computers in the 80’s. Nobody was pushing boys to do that, they just did. For some reason more men enjoy working with computers than women. I’ve worked with a few female coders, and they were good at their jobs, but women are definitely a minority in the field.
I probably would have gone into tech earlier if I’d had a female role model in tech. When my (male) friends started programming in high school, I was very interested and wanted to learn it too. But it literally didn’t occur to me that I could, until ten years later, when I was already far along in a study in the humanities. I ended up in data/ software development in the end, but it took me ten years longer because I didn’t realise earlier that it was a field I could get into if I wanted.
So long story short, it’s not just a matter of interest, there are societal factors that play a role too.
May have something to do with computers as they exist being defined by male psychology. Well, it’s understandable why swords, guns, rockets are, and same with computers.
Basically sending instructions to change state. I don’t know how can a computer exist which doesn’t work like this and is still usable for the humanity, but this seems to be psychologically a bit more of a male thing. Maybe there’s nothing problematic for women but aesthetics there.
If it’s something deeper, then maybe some analog optical\quantum\whatever computers of the future will push us to change paradigms for some drastic change in efficiency. And maybe those new paradigms will be more appealing to women.
Which is ironic, because women were the “code monkeys” of back when human computers were a thing - humans actually doing the computing by hand; and most of them were women.
this mentality made me doubt and question and delay for too long so i try to push back on it when i see it. You don’t actually need to have always “known” or “shown signs”. If you feel like experimenting you can just try it.
Can we talk about annotations which are broken when you upgrade spring boot ? You are asked to upgrade some old application to the newest version of spring boot, application that you discover on the spot, the application does not work anymore after the upgrade, and you have to go through 10 intermediate upgrade guides to discover what could possibly be wrong ?
An application I’ve never heard or seen before that needs to be upgraded, and it breaks, so you now need to understand what the hell this application does so you can fix it properly.
Gradle, with it’s transitive dependency modifications is a huge pain in this area.
It used to be that if a library ended up having a flaw then it would be flagged and we would get the dependency updated. These days security block the “security risk” and you have to replace your dependencies dependency. Fingers crossed you can get it to actually test all the code paths.
If an second level project gets a flaw, and it’s used indirectly then we should really look at getting the import updated so that we know it works. If that import is abandoned then we should not be updating that second level dependency, either adopt and fix the first level dependency or look at an alternative.
Spring annotations in general. There’s a completely hidden bean context where every annotation seems to throw interceptors, filters, or some reflection crap into. Every stacktrace is 200 lines of garbage, every app somehow needs 500mb for just existing and if you add something with a very narrow scope, that suddenly causes something completely unrelated to stop working.
Realistically, DI and all the Spring crap does not add anything but complexity.
Our Spring service was so simple until we decided we needed annotations to handle the fetching of settings. Now we are corrupted with needless reflection.
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.