|
Canine Blues Arooo posted:This guy is just a factory of really stupid poo poo: Congrats dude, you described vaporware.
|
#
?
Nov 11, 2021 11:40
|
|
|
|
| # ? May 10, 2024 12:15 |
|
|
He’s right but only because people who join the communities tend to be technologically illiterate (although they probably think they’re cutting edge) and easily impressed. e.g. someone who fundamentally doesn’t understand that digital goods can be copied and is therefore impressed by NFTs, someone who has never used Google Sheets at work and is therefore impressed by a ‘product’ which is really a spreadsheet, people who were born after beenz and therefore think crypto tokens for micropayments are a really cool idea. There are more people who don’t understand tech and people willing to exploit them than there are of us, so these people will win.
|
|
#
?
Nov 11, 2021 12:16
|
|
|
It doesn't do me any harm if they bilk some rubes (it's always happening somewhere), but I really don't want this stuff to gain mainstream acceptance to the point that I'm forced to use it
|
|
#
?
Nov 11, 2021 12:49
|
|
|
Canine Blues Arooo posted:This guy is just a factory of really stupid poo poo: He just described SA. Lowtax = genius? /s
|
|
#
?
Nov 11, 2021 13:36
|
|
|
cum jabbar posted:It doesn't do me any harm if they bilk some rubes (it's always happening somewhere), but I really don't want this stuff to gain mainstream acceptance to the point that I'm forced to use it There's nothing to use so I wouldn't worry too much.
|
|
#
?
Nov 11, 2021 15:46
|
|
|
cum jabbar posted:It doesn't do me any harm if they bilk some rubes (it's always happening somewhere), but I really don't want this stuff to gain mainstream acceptance to the point that I'm forced to use it use it for what? crypto's value is wildly volatile so it's pretty useless as a currency.
|
|
#
?
Nov 12, 2021 01:33
|
|
|
prom candy posted:use it for what? crypto's value is wildly volatile so it's pretty useless as a currency. and medium of exchange works better when it’s not using hundreds of kilowatts per transaction
|
|
#
?
Nov 12, 2021 07:45
|
|
|
https://www.youtube.com/watch?v=RUwhX-c9JyA Sorry not sorry.
|
|
#
?
Nov 12, 2021 12:11
|
|
|
Devops guys are giving me a loving headache. I asked for a security token needed for setting up an automated scan because the instructions written by the devops guys told me to. They tell me to generate it myself, and when it fails, they tell me that only the tokens generated by admins work right now, but they're currently working to fix that. I ask for a status update the next day and the loving guy I asked for the security token from in the first place asks me why the other devops guy (who wrote the instructions) hasn't given me a token. Finally another developer who was in that group chat just hands me the token (generated by the guy I asked) that everybody else had been using for their scan. Do they even loving talk to each other? Rubellavator fucked around with this message at 16:27 on Nov 12, 2021 |
|
#
?
Nov 12, 2021 16:23
|
|
|
Rubellavator posted:Devops guys are giving me a loving headache. I asked for a security token needed for setting up an automated scan because the instructions written by the devops guys told me to. They tell me to generate it myself, and when it fails, they tell me that only the tokens generated by admins work right now, but they're currently working to fix that. I ask for a status update the next day and the loving guy I asked for the security token from in the first place asks me why the other devops guy (who wrote the instructions) hasn't given me a token. Finally another developer who was in that group chat just hands me the token (generated by the guy I asked) that everybody else had been using for their scan. They probably despise each other
|
|
#
?
Nov 12, 2021 16:31
|
|
|
ah yes the old gambit where DevOps implies that engineering teams can now "manage everything by themselves" DevOps promptly write documentation for each part of the infrastructure separately (mostly consisting of "look at the docs of tool X, version 0.3") but leave out all the documentation on how to connect the custom elasticsearch deployment to the custom metrics backend to the custom ci/cd pipeline management wrapper
|
|
#
?
Nov 12, 2021 18:34
|
|
|
The more senior your job title, the more one of your duties is to make friends with someone in devops. It’s the only way to get work done. My favorite boss used to take smoking breaks with a high end member of the database team. We were never blocked by the database team.
|
|
#
?
Nov 12, 2021 18:57
|
|
|
Sagacity posted:ah yes the old gambit where DevOps implies that engineering teams can now "manage everything by themselves" We must work for the same company. Don't forget that on top of everything you mentioned they incorporate a new shiny half-baked open source tool into the process every couple weeks and tell us it's the only thing we can use. Che Delilas fucked around with this message at 19:53 on Nov 12, 2021 |
|
#
?
Nov 12, 2021 19:47
|
|
|
“Oh yeah, those instructions are wrong, we should update them.”
|
|
#
?
Nov 12, 2021 20:28
|
|
|
Don't worry, you get a month to migrate to the new tool. You have time for that, right?
|
|
#
?
Nov 12, 2021 22:51
|
|
|
smackfu posted:“Oh yeah, those instructions are wrong, we should update them.” Sagacity posted:Don't worry, you get a month to migrate to the new tool. You have time for that, right? 
|
|
#
?
Nov 12, 2021 23:02
|
|
|
We're migrating all of our applications to the ~cloud~ and have a hard deadline of Monday, that conversation took place over 4 days, and I left out the part in the middle where it took me 2 days to get the scan to actually complete because it kept running out of memory.
|
|
#
?
Nov 12, 2021 23:07
|
|
|
Rubellavator posted:We're migrating all of our applications to the ~cloud~ and have a hard deadline of Monday, that conversation took place over 4 days, and I left out the part in the middle where it took me 2 days to get the scan to actually complete because it kept running out of memory. Are all your applications in the cloud now?
|
|
#
?
Nov 16, 2021 00:56
|
|
|
Good process: when you begin development of a relatively minor feature in november 2020, and maybe barely finally just pass the final test gate in december 2021 startups getting eaten big big old venerable enterprise companies is the literal worst and I want to carve my eyes out with glass
|
|
#
?
Dec 15, 2021 22:30
|
|
|
ChickenWing posted:Good process: when you begin development of a relatively minor feature in november 2020, and maybe barely finally just pass the final test gate in december 2021 I left my last company when we hit ~20 employees to join a company with fewer than 5. I'll do it again.
|
|
#
?
Dec 15, 2021 22:32
|
|
|
I was just in a triage meeting with 20 people. If they don't split up the team I gotta go, it's way too much noise. Nobody knows anything about most of the stuff.
|
|
#
?
Dec 15, 2021 23:24
|
|
|
I absolutely hate those meetings. It always just gets hijacked and nothing good happens.
|
|
#
?
Dec 16, 2021 05:13
|
|
|
I don't want to go to a party with that many people, much less a meeting
|
|
#
?
Dec 16, 2021 06:19
|
|
|
prom candy posted:I left my last company when we hit ~20 employees to join a company with fewer than 5. I'll do it again. I consider that more strongly by the day We're having serious issues about siloed information between the UI team and the application team and people have been discussing just merging the teams and I think I will kill myself if we add even more noise to our sprint planning
|
|
#
?
Dec 16, 2021 15:04
|
|
|
I really enjoy working on super small teams. It means I'll probably never get to work on some huge flashy product but that's ok, I'd rather just have mostly good days at work.
|
|
#
?
Dec 16, 2021 15:10
|
|
|
99.9% of big projects are boring heaps of junk anyhow. You probably have just a big a chance finding a small project that is flashy/becomes flashy.
|
|
#
?
Dec 16, 2021 16:05
|
|
|
My org's UX team has been in a constant state of internal warfare since at least the start of the year, unable to agree on a coherent vision for the product's esthetic (or even a single prototyping tool). They've rotated through at least 6 new hires, none of which have lasted more than a month or two before deciding to flee, but each started just long enough to propose their own set of drastic changes to product and have engineering get halfway through revamping before someone else shows up to give their own conflicting set of drastic changes, preoccupying engineering resources that are desperately needed elsewhere.
|
|
#
?
Dec 16, 2021 16:41
|
|
|
a dingus posted:99.9% of big projects are boring heaps of junk anyhow. When a project reaches a certain size it really means it should be multiple smaller ones because big projects only ever end one way.
|
|
#
?
Dec 16, 2021 17:56
|
|
|
What? You DON'T want to work on a 20 year old monolith comprised entirely of hacks made by people that aren't there anymore?
|
|
#
?
Dec 16, 2021 22:17
|
|
|
Have you ever thought about how horrible the world would be if fart smells never disappeared? Working in development is just like that. 'Code smell'
|
|
#
?
Dec 16, 2021 22:23
|
|
|
wilderthanmild posted:What? You DON'T want to work on a 20 year old monolith comprised entirely of hacks made by people that aren't there anymore? But enough about Salesforce.
|
|
#
?
Dec 17, 2021 00:07
|
|
|
wilderthanmild posted:What? You DON'T want to work on a 20 year old monolith comprised entirely of hacks made by people that aren't there anymore? Better than a 20 year old monolith comprised entirely of hacks mostly written by the guy who is now CTO
|
|
#
?
Dec 17, 2021 21:04
|
|
|
Sign posted:Better than a 20 year old monolith comprised entirely of hacks mostly written by the guy who is now CTO Having to tip toe around hiding that you're removing the CTO's code. Dev: "We have to rewrite the call scheduling component so it may delay this project a bit" CTO: "What do you mean?! I Wrote that. It works perfectly. WHY ARE YOU DOING THIS? ARE YOU TRYING TO RUIN MY SYSTEM!?"
|
|
#
?
Dec 17, 2021 22:40
|
|
|
I worked somewhere like that, every time something exploded the last commit was the CTO and it was fixed without that fact coming up. The guy was a mediocre developer and a terrible manager who ended up as CTO due to tenure which always ends well.
|
|
#
?
Dec 17, 2021 22:43
|
|
|
Chief Technical Officer more like Cut Tête Off
|
|
#
?
Dec 17, 2021 22:47
|
|
|
My product owner just asked if we can handle .RAR files. Nah buddy, I'm sorry, this is 1991, the technology just isn't there yet.
|
|
#
?
Dec 17, 2021 22:58
|
|
|
Sign posted:Better than a 20 year old monolith comprised entirely of hacks mostly written by the guy who is now CTO My last job was kind of like this, except instead of the CTO he became combination lead sales engineer and product owner. The codebase had grown considerably (by people stapling things over top of what was there, naturally) since he'd changed roles, and he hadn't seen it for at least 7 years when I started there. The old folks in this thread might guess what tended to happen: he didn't trust any estimate we gave him, thought we were sandbagging, because his memory of the code and the customer base were both years out of date. So he gave the customer time estimates that were generally about half as long as it tended to take (usually by cutting our estimates in half), and then complained about how the customers were angry when reality hit.
|
|
#
?
Dec 18, 2021 10:01
|
|
|
Let me tell you about my new job. I started it 3 weeks ago, and I have done 1, one [1]. Ticket. The onboarding process was 2 weeks long. For 6 hours a day, of meetings. That was 10 solid days of meetings, with long-winded powerpoint-based introductions to every single department and the nitty gritty details of what they do. Those two weeks end, and I finally get to actually spend more time with my team, and the bullshit meeting culture continues. We have chapter meetings once a week, retro once a week, refinements once a week, all 3 of those meetings take 2 hours each. Then there's standup which takes an average of a hour and a half. Half an hour to go through the board for the nitty gritty details, then an extra hour for 'after standup' where the devs discuss the exact technical execution of their work and the direction of the product. Then there's developing. I work on the front-end, no problem. Branches have to be named a specific way, not too weird, but they can NOT NOT be named that way or it will trigger a build which will block the other builds and after about an hour it'll break, because the branch is named wrong. Then there's the back-end. Naturally dockerised because why not, everything needs to be containerised but you only bring up containers X, Y and Z if you want to run locally. Oh and auto-reload won't work on the application when you make modifications because its an Angular 2 application living inside an AngularJS application. So you need to build the full application in iDEA and run it as dev, then run the Angular application in vscode/webstorm and if you make changes you have to manually refresh because, as I said, auto-reload doesn't work. But wait, there's more. If you pull dev for the back-end you have to go through the whole process of downing the containers and bringing up each individual container in the right order. Then you rebuild dev and it might just break for some reason because there's instability in the configuration. I'm not a Java dev, I don't know or care. Then there's opening a PR, hoo boy do you open a loving PR. First you push your very specific branch to the UI application repo. Then you go back to the main repo, and create a new branch WITH THE EXACT SAME NAME and push that to the main app repo. Then you go back to your UI repo, and push an empty commit to it. This will trigger a script somewhere that updates the PR to the main repo with some loving update to the docker version or some absurd garbage. Once thats done, THEN your UI PR can be approved and merged, and once thats done you create a ANOTHER commit to the MAIN repo with a git tag. This is chaos. This is pure loving chaos. This company is absolute loving nonsense.
|
|
#
?
Dec 20, 2021 11:56
|
|
|
|
|
#
?
Dec 20, 2021 13:03
|
|
|
|
| # ? May 10, 2024 12:15 |
|
|
You'll be a hero if you come up with a dummy test backend that makes the UI easy to run on its own. These people might be too sloppy to appreciate the benefit, though...
|
|
#
?
Dec 20, 2021 13:08
|
|