For anyone wondering what a document should look like, the DoD publishes that for anyone to read. Just search Derivative Classifier Training. Spoiler alert: this ain’t what a top secret document looks like.
I watch too many videos on expensive guitar pedals I can’t afford.
I’m “on the bench” at the outsourcing company I work for and I am starting to seriously consider going into DSP programming just so I can work on doing this to effects controls.
I want to make knobs available for this this this and this parameter.
In my experience it doesn’t matter. You have to regularly refactor your code to keep up with new features. The more often you can make time to do it the easier it is.
Unit test to help catch regressions. If you are confident in your test catching a good portion of bugs from refactoring, at least you feel confident refactoring. Worst case, at least you ensured your code is testable. There is nothing worse than refactoring untestable code.
Self-documenting code and when it fails to self-document, comments or refer to a wiki page.
In my first month at my current employer, I added some temporary code with a TODO to fix it properly. That was 11 years ago in 2013, and the same TODO is still there today, and these days it’d be significantly harder to do it. 😂
My homeoffice setup is right next to a window, so it’s too bright for dark mode during the summer. So I work in light mode from about April-September and in dark mode for the rest of the year
Any day you/your company could potentially be contacted by a 3 letter agency and/or the police to pull the data from a specific user for an investigation. “ESI request” is a term I hear on occasion.
It’s a good idea to be on good terms with your employers lawyers.
It’s mind bending that there are actual humans on the planet, paid a shit tonne more than software developers, who not only believe the parody highlighted by @SwiftOnSecutity, but treat and share it as gospel, acting on it with nutjob metrics to “increase productivity” whilst salivating over the hyperbole around “AI” that is sweeping the globe, dreaming of a better world.
One without those pesky developers with their brains, thoughts and opinions.
But, what do I know, I’ve been in this profession for only 40 years…
You’re probably not the biggest asshole in the room. In my experience, the person making decisions (and the most money) is never the most qualified, most competent, most efficient, or hardest working individual. They are just the biggest asshole in the room. They’re willing to be loud and belligerently wrong, they’re willing to take credit for the accomplishments of others, they’re willing to shift blame onto someone else, they’re willing to demand everyone else work harder than they do, and they’re willing to demand far more than their fair share of the profit.
And they will be mollified by the rest because nobody is a bigger asshole. Most people just want to do their jobs, and don’t want to rock the boat. Competent people see opportunity to ride in the wake of the biggest asshole in the room.
If you ever watch Shark Tank, you’ll see they are masters of the craft.
The problem is that most of us have swallowed the ‘competence uber alles’ ideal that school fed us through exams and scoring, when the game really is mostly politics (as in interpersonal relationships). So we are understandably disappointed when the incompetent get promoted through brown nosing or luck, when we should be reevaluating the rules of the game.
That’s always fun in sales. The vendor that brazenly promises two-and-a-half mirage for half the price will win the bid, and the sales people will move on to a different employer when the real budget for the project becomes clear.
I used to joke with my niece that my programming job was just me staring at screens and meetings all day. She didn’t believe me until she got to shadow me one day and got super bored.
Not op but guessing she had an idea from media like TV shows and movies that make technical jobs seem much more exciting for entertainment over realism. Crises are usually more Jerry accidentally deleted a directory and we need to recover some files and establish safe guard procedures to prevent it from happening again or this thing broke that nobody even knew existed so we gotta figure it out and less type fast enough to save the mainframe from l33t hackers.
They do the same thing building architects do. They draw pretty pictures of the end product that may of may not be structurally sound, then rely on engineers to build it and make sure it doesn’t collapse.
I tried to get a software architect to explain their job to me once, it was like a “lean startup”, a libertarian, and a psychic had written an elevator pitch together.
I disagree with not needing dedicated architects at least once you reach a certain size. If there are 50 plus developers working on a dozen or more projects there’s a large communication cost to stay on top of everything.
I always saw architects roles in modern development being the person trying to find synergies between different teams andcoordinateing them working with each other.
Like if some team makes a sick project for managing streams of data streams the architect should be promoting it for other teams to leverage.
That’s one role, as a software architect I also often served as the sunk cost fallacy bad news delivery system. It’s a good idea to keep some eyes from outside your team on your project just to do the occasional sensibility check.
There is also a large responsibility to make sure different teams are well coordinated and not building the system in directly opposing directions. It really fucking sucks to have your work, as a developer, invalidated by someone else’s work suddenly without any warning.
The good ones: design and adjust software development processes, standards for cross-project functionality and reusability and in general try and improve at a high level the process of making, maintaining and improving software in a company.
The bad ones: junior/mid-level software design with a thick layer of bullshit on top to spin it as advanced stuff.
If you want to see bad software architecture, just look at most of Google’s frameworks and libraries.
programmer_humor
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.