|
Vulture Culture posted:Most documentation is only useful if people read it, and companies like Atlassian make it very hard to understand how people are engaging with content on their platforms. Think about why, even though tracking views is one of the easiest and cheapest features they could possibly implement, it's in their best interest not to surface this information
|
#
?
Apr 1, 2024 14:11
|
|
|
|
| # ? Apr 19, 2024 16:48 |
|
|
Sagacity posted:Confluence has this feature though? So not sure why you're singling out Atlassian here. Vulture Culture fucked around with this message at 16:14 on Apr 1, 2024 |
|
#
?
Apr 1, 2024 16:12
|
|
|
Answering a question with 'read this page I wrote months ago'' is a highly fulfilling feeling
|
|
#
?
Apr 1, 2024 17:34
|
|
|
If I added the number of times that someone has asked "where is this documented?" after someone answers a question, as if they should never have to ask anyone for help or figure something out for themselves, to the number of times the same person has asked a question with a clearly documented answer, I'd have a large number.
|
|
#
?
Apr 1, 2024 17:43
|
|
|
Lemma: only support-centric teams have documentation in their wikis that's both useful and necessary.
|
|
#
?
Apr 1, 2024 18:45
|
|
|
Thing with docs is that if you really want to bother with *any*, it's sort of all or nothing. Either setup dedicated docs SSGs so your team can easily edit markdown in the same commit, or don't bother. If all you can actually do is a sort of manual / half assed "expectation" that ppl will update the confluence, then don't bother. If setting up markdown docs SSG sounds too onerous then it's probably not actually as important as you think it is. It's just not convincing to me that someone says something is mandatory, zero-fail or mission-critical but won't actually engineer something to support that. Confluence is a wiki for fast business docs and project mgmt. Technical docs are a feature of the product. Oysters Autobio fucked around with this message at 15:36 on Apr 7, 2024 |
|
#
?
Apr 7, 2024 15:31
|
|
|
Oysters Autobio posted:Thing with docs is that if you really want to bother with *any*, it's sort of all or nothing. Isn't that just literally having markdown file inside git repo on github/gitlab/any good git frontend?
|
|
#
?
Apr 7, 2024 17:41
|
|
|
Oysters Autobio posted:It's just not convincing to me that someone says something is mandatory, zero-fail or mission-critical but won't actually engineer something to support that. 
|
|
#
?
Apr 7, 2024 23:25
|
|
|
Oysters Autobio posted:It's just not convincing to me that someone says something is mandatory, zero-fail or mission-critical but won't actually engineer something to support that.
|
|
#
?
Apr 13, 2024 18:50
|
|
|
oof ouch my
|
|
#
?
Apr 13, 2024 19:02
|
|
|
Dang that's like tech_debt.txt copy pasta
|
|
#
?
Apr 13, 2024 19:20
|
|
|
ChickenWing posted:oof ouch my MBAs will do anything to not pay down tech debt
|
|
#
?
Apr 13, 2024 20:18
|
|
|
Clanpot Shake posted:MBAs will do anything to not pay down tech debt I mean, if your company is hiring MBAs for literally anything they deserve to fail.
|
|
#
?
Apr 13, 2024 21:08
|
|
|
Clanpot Shake posted:MBAs will do anything to not pay down tech debt Any MBA born after 1993 can't manage... all they know is charge they laptop, "work," be business , cause tech debt and lie
|
|
#
?
Apr 13, 2024 21:30
|
|
|
I was just saying the other day that my company doesn't seem to take competitive threats seriously enough and asked "don't we have any piece of poo poo MBAs with a coke problem in this company" I certainly don't want them running the show but in a small and competitive market where I have equity I want at least one greasy paranoid piece of poo poo in my deck.
|
|
#
?
Apr 14, 2024 18:15
|
|
|
Volmarias posted:Any MBA born after 1993 can't manage... all they know is charge they laptop, "work," be business , cause tech debt and lie can we make this the title of every thread on the forums
|
|
#
?
Apr 14, 2024 19:34
|
|
|
lol yeah I should've caveated that with an ironicat or something
|
|
#
?
Apr 14, 2024 20:44
|
|
|
we've been mandated to switch from confluence release notes to jira releases i am not allowed permissions to create/edit releases for, allegedly, ISO reasons. as a sysadmin i have access to the jira master admin account but i am not allowed to use it to give myself the perms, so instead i slack the head of engineering for every release setup, update, typo fix, and date update.
|
|
#
?
Apr 17, 2024 06:05
|
|
|
Every time our executives open their mouth, they expose how ignorant they are about software engineering. Maybe this is self-evident to everyone, but I just gotta yell it into the void.
|
|
#
?
Apr 17, 2024 14:38
|
|
|
xiw posted:as a sysadmin i have access to the jira master admin account but i am not allowed to use it to give myself the perms, so instead i slack the head of engineering for every release setup, update, typo fix, and date update.
|
|
#
?
Apr 17, 2024 15:04
|
|
|
a quote from teams the other daymanagers.txt posted:[4:02 p.m.] <manager> 
|
|
#
?
Apr 17, 2024 15:19
|
|
|
downout posted:Every time our executives open their mouth, they expose how ignorant they are about software engineering. god SAME
|
|
#
?
Apr 17, 2024 22:40
|
|
|
downout posted:Every time our executives open their mouth, they expose how ignorant they are about software engineering.
|
|
#
?
Apr 17, 2024 23:50
|
|
|
downout posted:Every time our executives open their mouth, they expose how ignorant they are about software engineering. Half of our stack is running on an end of life transport layer and nobody cares. Is that better or worse than what you're dealing with?
|
|
#
?
Apr 18, 2024 00:48
|
|
|
Sagacity posted:I suppose you're conversely fully up-to-date on how to run a company then 
|
|
#
?
Apr 18, 2024 04:02
|
|
|
downout posted:
ftfy Clanpot Shake posted:Half of our stack is running on an end of life transport layer and nobody cares. Is that better or worse than what you're dealing with? Don’t doxx me.
|
|
#
?
Apr 18, 2024 04:17
|
|
|
Sagacity posted:I suppose you're conversely fully up-to-date on how to run a company then 
|
|
#
?
Apr 18, 2024 06:59
|
|
|
Sagacity posted:I suppose you're conversely fully up-to-date on how to run a company then Yeah bud, I'm just as qualified as the average CEO to run a company: not at all
|
|
#
?
Apr 18, 2024 07:23
|
|
|
Clanpot Shake posted:Half of our stack is running on an end of life transport layer and nobody cares. Is that better or worse than what you're dealing with? OK, I'm curious now  What transport layer?
|
|
#
?
Apr 18, 2024 09:15
|
|
|
I had this aha moment this year where I realized that to get to a certain level of leadership, you have to either be the least curious person imaginable or manage your curiosity by being an rear end in a top hat to people trying to bring you fascinating problems. You cannot afford to be in a meeting and hear something so deeply engaging and interesting that it occupies your headspace, turns your gears, and makes you tune out the soul-crushing, boring poo poo that's important to the operation of the business CEO skills are like being a distance runner: conceptually, there is virtually nothing hard about the job; you put one leg in front of the other, a lot of times. But doing it half competently requires a level of persistence that I hope to never need or have Vulture Culture fucked around with this message at 15:09 on Apr 18, 2024 |
|
#
?
Apr 18, 2024 15:05
|
|
|
What you're chasing with interesting problems is insight and knowledge. A CEO is just chasing money.
|
|
#
?
Apr 18, 2024 15:24
|
|
|
Our engineering VP goes on sabbatical soon, but as yet the team leads are still in the stone age. The new manager gets that workload and was very clear that the teams are answerable for fixing broken processes, lack of clear project goals, deadlines, estimates, it's on the teams to make something work. Engineers on one team took the initiative, used this chance to share ideas about what to improve in the next few months. Yesterday the lead told one of the 5yr engineers on the team that they had to change how they reviewed code. Production libraries, one off simple scripts, prototypes,... after four weeks of being told to focus on what matters, the highest priority for the team: Code style according to a manual checklist that the lead doesn't even follow. I asked the engineer if they agreed that was the highest priority. Naup. Enough is enough. Lead won't listen to or engage engineers on the team, doesn't trust them, give them space to grow, doesn't even seem to know role responsibilities in the org.
|
|
#
?
Apr 19, 2024 05:38
|
|
|
Where did you get your team leads from?
|
|
#
?
Apr 19, 2024 12:22
|
|
|
|
| # ? Apr 19, 2024 16:48 |
|
|
PhantomOfTheCopier posted:Our engineering VP goes on sabbatical soon, but as yet the team leads are still in the stone age. The new manager gets that workload and was very clear that the teams are answerable for fixing broken processes, lack of clear project goals, deadlines, estimates, it's on the teams to make something work. Engineers on one team took the initiative, used this chance to share ideas about what to improve in the next few months. a) Why is one person, being asked to make lightweight and modest changes to their operating process, a problem that demands understanding of prioritization? b) Why does any person in your org, lead or otherwise, need to behave perfectly and avoid being seen as a hypocrite in order to make or suggest improvements? I ask my kid all the time to clean up her plate when she leaves the table, sometimes while my own plate is still at the table. This is sometimes frustrating to her, but there shouldn't be a situation where the first person to do the wrong thing (for some person's definition of "the wrong thing") becomes accountable for taking care of it for every person that follows. You clean up your place now because you're still where the mess is, and that's how we do it here. I'll come right back and do mine. Mea culpa. Honestly, it comes across that the problem is that you, your coworker, and potentially other folks don't like working with this person. That's okay. But focus there and have the conversations about that, not about some made-up prioritization reason. Vulture Culture fucked around with this message at 15:57 on Apr 19, 2024 |
|
#
?
Apr 19, 2024 15:53
|
|