No Microsoft Access is/was a GUI software actually meant to have databases instead of how everyone uses Excel/spreadsheets as databases. It is a part of the office suite. It works pretty much like traditional databases but has an easier to access GUI for non programmers I guess. I don’t think it’s used a ton nowadays except for legacy processes that haven’t been updated.
No its microsofts database GUI program that’s part of Microsoft Office . imagine software made for users who have a vague understanding of SQL and visual basic but then an exec. forced the designers and devs to make it accessible to everyone while giving them barely any teamembers causing a fuckton of technical debt and unintuitive quirks , making anyone who opens the software feel like they have just been placed in a highly equipped tank , in front of a wall of unlabeled levers and told to drive the tank , or at least that’s how I view it.
(reposting from another account sorry if you see both comments)
We use it at work for it’s actual intended purpose: as a small database that isn’t customer facing. It’s used and maintained by nontechnical staff to keep data about equipment (slot machines).
It would be too much info for excel, but it’s not enough to really need anything more.
As an aside, I recall the early days when @SwiftOnSecurity was purposely ambiguous about the distinction between the artist Taylor Swift and their technology tweets. It was delicious to see confused responses.
At some point it changed. Not sure what triggered that. I have a vague memory of a stroke, but I might be misremembering.
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.
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.
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.
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.