Okay so my co-workers explains why they give me the title "GitHub Maid":

Basically most of the time the engineering didn't have the time to scroll through issues, and that includes me, so a lot of this stuff does not get triaged properly when reported. When I stumbled on the tracker, I knew I had to do something, so I sorted and sorted and managed the tickets by my own.

So being a "GitHub Maid" is not something to be embarrassed about after all, in fact, I think the dev team owed me a lot because the issue tracker is more organized, and the issues are getting triaged and assigned properly now compared before.

So if they call you like something similar, be proud of it because some developers wouldn't even bother to tidy up issue tracking.

I've fixed all the bugs in the issue tracker that are "fun to solve". What remains are vague reports of unexpected behavior.

Today is going to be tough 😫

The Steam Community forums for the Planet Zoo beta have really reinforced my decision to stay far away from game development.

A third of the posts are people who clearly have no idea what a beta is - "don't buy, too buggy". Sorry, were you expecting a finished game? You wasted your money, then.

Another third of the posts are people making decisions for the developers. A very common discussion is "Should they delay launch?" which makes my blood boil a bit. First of all, you have no fucking clue what kind of manpower this development team has. You don't manage them, and neither do I. So, neither you nor I should be making assumptions about how fast they can fix the issues, and definitely shouldn't make decisions about if the game should delay launch.

Second of all, neither you nor I know how the game is built. These fixes could mean a line of code, or they could mean a re-write of multiple core systems. We don't know, and I'm guessing you've probably never even written a line of code in your life so you REALLY shouldn't be telling these guys how to do their job.

The last third is benign discussion - people reporting bugs (even though there's an issue tracker, but that thing is fucking jam packed with 250 pages of reported issues), asking how to do xyz, posting feature requests, etc.

But if roughly 60% of the community is behaving poorly and actively working against development by pissing off the devs and drowning out constructive discussion, then yeah; I won't be going near game dev any time soon. Sure, developing business software means dealing with REALLY dumb people but at the very least they are in a business environment and not in a toxic forum of bullshit.

Oh, and as a closing remark, I love this game!

TL.DR.: Emojis in commit messages + bad commit messages made by Microsoft™ employees.

Yes, I'm looking at you Microsoft. It would be helpful if I can, you know, understand your commit messages instead of trying to guess wtf _that_ emoji means. That is, if it is the same emoji on my machine. We didn't figure that one out yet. And no, "Some 💄 changes ✨" is not a good commit message, even if you interpret it correctly (which depends on your emoji icon set).

idk about you, but that shitty 💄 emoji tends to be (see image) and I happen to associate that with an XLR audio cable. I had to ask someone else to understand a commit message; a message supposed to be explicit—stating what you changed and optionally why you changed it (you can off-load that part to an issue tracker).

Furthermore, that "Some 💄 changes ✨" commit did none of that. "I made cosmetic changes somewhere for some reason without linking to an issue." If you didn't catch that little detail yet: "COSMETIC CHANGES" is vague as fuck. What is a cosmetic change?

* Does a cosmetic change mean adjusting indentation?
* Does it mean deleting unnecessary abstraction to make the code more readable?
* Does it mean refactoring code to add that beauty factor?
* Does it mean all of the above? Or perhaps a specific combination of these?

Human communication is shit enough, don't make it worse than it already is.

Me : I found this code issue, I think we need to fix it
PO: does it affect the user?
Me: not really but we can make it better
PO: do you have a defect for it in *insert issue tracker here*
Me: no, I just noticed it
PO: is there an IM ticket for it?
Me: I don't think so
PO: is this issue already in production?
Me: possibly. Yes. That's why I was wondering if we should fix it.
PO: okay then we will fix it in the 3rd release from now if you still remember it by then.

New issue tracker has a dedicated screen for every issue. Noice!

Don't bother programming anything for us. We'll never use it. (I work at an IT help desk Technician at a school and this was from the IT director)

They now use 3 of my projects (one SSO authentication, another issue tracker, and the other inventory)

This might not resonate with many ranters here... but FUCK Taylor Otwell & Graham Campbell.

Like, not on a personal level. Maybe they're great to drink a beer with. But as framework devs... fuck everything about them.

Laravel seems so nice, it takes away many annoyances of developing in PHP. Collections are the array object you've always needed. The route bindings, middlewares, request validation objects, it's all sweet.

But eventually your company serves a few million customers, you run into specific performance problems or missing features on a deeper level. You open the issue tracker... and see a few hundred issues about the problems you are encountering, they already exist.

Some just have a short paragraph with a request for a feature, some complete PRs with tests in the style of the framework. All of them closed.

Reasons?

"We don't think anyone will ever need this"
"This seems complicated, you can just do <super non-DRY hacky code>"

FUCK YOU WITH YOUR TODO APP SNIPPETS AND USER-POST-ARTICLE EXAMPLES. I'M NOT BUILDING THE NEXT WORDPRESS. I'M DEALING WITH THE REALITY OF GRAPH DATABASE CLUSTERS, COMPLEX AUDITING LOGS AND A GAZILLION QUERIES PER SECOND.

Sigh... the problem with all these "simple" and "elegant" languages & frameworks is that they don't fucking scale.

Not because the language, server or framework intrinsically can't do it, but because the maintainers are stuck thinking in terms of their retarded non-realistic example apps.

I think I'll go back to my cave and write some Haskell or Rust to calm down.

when testers add issues to the issue tracker and the body is just "it doesn't work"

When a repos issue tracker looks more like Stack Overflow in it's content...

Spent a good hour wondering why our website is displaying in the wrong language on some phones. Ended up opening an issue on the Chromium tracker.

-- Best --
> Submitted my notice of termination for my current job
> Found a new job starting next year
> Can switch from Windows to Linux/MacOS in new job
> Got more time to work on personal projects due to the pandemic

-- Worst --
> Huge amount of software restrictions (current job) almost got several projects at work canceled. Maybe its important to say that the core business of my current workplace is auditing so there are a lot of law regulations which then apply in the softwaredevelopment process.
> New managers that do not have the slightest clue of what they're doing
> Online Teambuilding events
> Absurd amount of segmentation of tools and also different coding guidelines that are used at work. E.g. one team uses jira, another trello, another github issue tracker and so on.

I set up an issue tracker for a software I'm developing for a company. Sent them an invitation to that tracker, stating that I hope to keep discussions more concise and clear that way (they're all HW/Embedded Devs)

The good news is: they've taken to the tracker quite well and are happily reporting issues and discussing them.

The bad news is: they're all sharing a single account.

It's been up for a day now and already no one knows anymore who reported/commented what.

WHY, JUST WHY would you think it's a good idea to share an account between 5 people, maybe more, who knows? Creating one takes less than a minute and it's free ffs.

When the CTO/CEO of your "startup" is always AFK and it takes weeks to get anything approved by them (or even secure a meeting with them) and they have almost-exclusive access to production and the admin account for all third party services.

Want to create a new messaging channel? Too bad! What about a new repository for that cool idea you had, or that new microservice you're expected to build. Expect to be blocked for at least a week.

When they also hold themselves solely responsible for security and operations, they've built their own proprietary framework that handles all the authentication, database models and microservice communications.

Speaking of which, there's more than six microservices per developer!

Oh there's a bug or limitation in the framework? Too bad. It's a black box that nobody else in the company can touch. Good luck with the two week lead time on getting anything changed there. Oh and there's no dedicated issue tracker. Have you heard of email?

When the systems and processes in place were designed for "consistency" and "scalability" in mind you can be certain that everything is consistently broken at scale. Each microservice offers:

1. Anemic & non-idempotent CRUD APIs (Can't believe it's not a Database Table™) because the consumer should do all the work.
2. Race Conditions, because transactions are "not portable" (but not to worry, all the code is written as if it were running single threaded on a single machine).
3. Fault Intolerance, just a single failure in a chain of layered microservice calls will leave the requested operation in a partially applied and corrupted state. Ger ready for manual intervention.
4. Completely Redundant Documentation, our web documentation is automatically generated and is always of the form //[FieldName] of the [ObjectName].
5. Happy Path Support, only the intended use cases and fields work, we added a bunch of others because YouAreGoingToNeedIt™ but it won't work when you do need it. The only record of this happy path is the code itself.

Consider this, you're been building a new microservice, you've carefully followed all the unwritten highly specific technical implementation standards enforced by the CTO/CEO (that your aware of). You've decided to write some unit tests, well um.. didn't you know? There's nothing scalable and consistent about running the system locally! That's not built-in to the framework. So just use curl to test your service whilst it is deployed or connected to the development environment. Then you can open a PR and once it has been approved it will be included in the next full deployment (at least a week later).

Most new 'services' feel like the are about one to five days of writing straightforward code followed by weeks to months of integration hell, testing and blocked dependencies.

When confronted/advised about these issues the response from the CTO/CEO
varies:

(A) "yes but it's an edge case, the cloud is highly available and reliable, our software doesn't crash frequently".
(B) "yes, that's why I'm thinking about adding [idempotency] to the framework to address that when I'm not so busy" two weeks go by...
(C) "yes, but we are still doing better than all of our competitors".
(D) "oh, but you can just [highly specific sequence of undocumented steps, that probably won't work when you try it].
(E) "yes, let's setup a meeting to go through this in more detail" *doesn't show up to the meeting*.
(F) "oh, but our customers are really happy with our level of [Documentation]".

Sometimes it can feel like a bit of a cult, as all of the project managers (and some of the developers) see the CTO/CEO as a sort of 'programming god' because they are never blocked on anything they work on, they're able to bypass all the limitations and obstacles they've placed in front of the 'ordinary' developers.

There's been several instances where the CTO/CEO will suddenly make widespread changes to the codebase (to enforce some 'standard') without having to go through the same review process as everybody else, these changes will usually break something like the automatic build process or something in the dev environment and its up to the developers to pick up the pieces. I think developers find it intimidating to identify issues in the CTO/CEO's code because it's implicitly defined due to their status as the "gold standard".

It's certainly frustrating but I hope this story serves as a bit of a foil to those who wish they had a more technical CTO/CEO in their organisation. Does anybody else have a similar experience or is this situation an absolute one of a kind?

So, as you may be aware, I work as solo dev for small company. There is easly enough work for team, but I digress..

So, they wanted to stay updated whats progress on some projects. We use slack. I use git. I set up account for them so they can come into my git and controll if issues are solved, etc. I wont get started about any dev ever beeing judged by how much code is outputted, beyond scope of this.

So they started bitching about that git is too technical and too complicated and shit. They made bizzare bullshit google excel (not even in polish) and stupidass form to "audit issues". Hmm.. wtf. I just didnt use it becouse it was slowing me down and was just frustrating, how one can replace git + issue tracker with fucking spreadsheet?!

Okay, so having that aside, I complained about that so they were like "okay, so you want to use git and we want to be notified. whats your solution" me "oh, you want to stay notified, thats easy, I can plug my git into slack"

Now our slack is spammed to oblivion with git notifications.

Now they are annoyed that they are too notified. (Yes I consulted with them what will be plugged into slack)

Oh well

¯\_(ツ)_/¯

I've got a user who keeps asking for weekly updates on a project I'm on and my pm is supposed to interface with them and give them the status. But my pm comes back to me like "so everything is good right?"

When we just talked last week about how it's not and I still have work stoppages. I have status updates written in our ticket tracker for him and he has tons of emails explaining the issue but he always forgets what the status is anyway!

Jesus, having to keep reminding someone of something when the information is right out there for them to grab quickly and easily is bloody annoying. He just neglects this one project! I'd cut out the middleman but I need him because I don't know enough about business rules to make decisions or ignore concerns that crop up in my planning!

If your comment on an issue tracker ticket starts with the word 'also' just take a minute and create a new bloody ticket. Especially if the original ticket is resolved and you're going to leave it as resolved.

Am I the only one whose daily morning routine is not only reading through devRant feed, but also catching up on the devRant issue tracker? Love me some discussions there :D

Reading someone's legacy package.json
{
.... stuff
"licence": ....,
"dependencies": { .... },
"bugs": "run for the hills"
.....
}
what is this? am I supposed to find an issue tracker in some unnamed hills

I know this is utopic, but I've been thinking for a while now about starting an open source platform for figuring out the problems of our society and finding real world, applicable, open source solutions for them.

To give you some more details, the platform should have two interfaces:
- one for people involved in researching, compiling issues into smaller, concrete chunks that can be tackled in the real world, discuss and try to find workable solutions for the issues and so on
- one for the general public to search through the database of issues, become aware of the problems and follow progress on the issues that people started working on

Of course, anyone can join the platform, both as an observer (and have the ability to follow issues they find interesting) and/or contributor (and actually work with the community to make the world a better place in any way they can).

Each area of expertise would have some people that will manage the smaller communities that would build around issues, much like people already do in the open source community, managing teams to focus on the important thins for each issue. (I haven't found a solution for big egos getting in the way yet, but it would be nice if the people involved would focus on fixing stuff in stead of debating about tabs vs spaces, if you know what I mean).

The goal of this project would be to bring together as many people from all kind of fields to actually try to fix this broken society.

It would be even better if it attracted people with money and access to resources (one example off the top of my head being people like Elon Musk) that could help implement the solutions proposed by the community without expecting to gain profit off of it (profit is also acceptable if it is made in a considerate, fair and helpful way, but would not be promoted on the platform).

The whole thing would be voluntary work; no salary, no other commitment than the personal pledge that once someone chooses to tackle something, he/she will also see it trough (or at least do his/her best).

The platform would be something like a mix of real time communication, issue tracker, project management tool and publishing platform.

I don't yet have all the details for how it should all fit together, but if there is something that I would like to start, this is definitely it!

PS: I don't think I can ever do something like this by myself, and I don't really have the time to manage a community of developers to start work on it right now. But if you guys think something like this is something worth your time, I will make time and at least start on defining the architecture and try to turn this into a real project.

If enough people are interested, I will drop any other side projects and do my best to get this into the world!

Thank you for reading :)

Hello god, I'd like to report a bug.
this.IsSocial is true, but this.BeSocial() throws a NotImplementedException.
I'd like this fixed ASAP, at least by changig this.IsSocial to false since the BeSocial method is not implemented, but this mismatch is killing me...

Anybody know the URL of gods issue tracker? I really need to file this bug...

I have nothing to do today. I could go Jack off in the bathroom for 3 hours, then go home and my boss would be proud of my hard work. He told me to leave him alone because he is busy today after I went back 10 time for more tasks. We don't use any issue tracker or anything, and I already commented all the code I have access to(microservices means it is all developed in small stand alone parts and I can only see mine. No repo....). But I get in chewed out if I seem unbusy!!!

Is there a collaborative tool to make a project plan, with UI mockups and other designs? Not a something like issue tracker or project timeline.

Looks like I am beginning my freelance journey.
Usefull Issue Tracker / Project Management tool?

If it's foss and written in python that would be great, I would probably try to extend it with extensions later on.

How can I tell if a package has been abandoned? I've had my eye on silber/bouncer for awhile but there's no sign of the dev in the issue tracker or in github anymore.

I am the technical lead in a project which uses a C# based framework. It's a lot of drag and drop, and C# scripts can be embedded for fancy stuff.

Scripts in general are not hard to do, it's harder to understand the business rules rather than the code itself.

I got hired as a junior to build this project from scratch as an MVP, and we need another junior to add enhancements and minor changes required from our end users. Since management wants me to move on working on more mid-senior development stuff, I'm supposed to be only supervising the juniors work (in the hopes that one day they'll be able to work on their own).

We've had bad luck filling this position. Our last hire is a guy like 17 years older than me, supposedly with experience in said framework but OH DEAR GOD.

Fucktard can't understand requirements and corrections, isn't able to deliver a 20 line script without fucking up. I give him a list with 3 mistakes to fix and only fixes two, crap like that.

Now, hear me out, the mistakes are stuff like:

- Unused variables
- Confusing error messages
- Error messages written in spanglish (mix between Spanish and English, we're located in Latin America)
- Untested features, this is the worst of all.

You may say "but he's a junior", sure. But as I said, he supposedly has experience, more years in IT than me, and fine, you're allowed to fuck up a few times on your first tasks but not make the same mistakes over and over, specially since we've already sat down and addressed these issues in presence of the CTO.

Fuck this guy. I genuinely dislike him as a person also, he is from another latin country and we have some serious cultural differences. For instance, he insists on sucking your ass constantly, being overly well manered (we already saluted with the whole team at the daily stand up, stop saying hello, good day, regards in each of your fucking chat messages or task submissions), and other mannerisms that are hard to translate, but whatever, all of these attitudes are frowned upon here. They're not necessary, we just want to keep it simple, cordial and casual and see you deliver the crap that you're being paid for with a decent level of quality.

On Monday the CTO comes back from vacation, I'm looking forward to that meeting, gonna report his ass, there is evidence everywhere on our issue tracker.

Why devRant is not open source?
I know that it has a Github issue tracker with a awful amount issues.
Wouldn't it be better if people could work on the platform to improve it since most of the devRant users are developers.
(Just a random thought i had)

What's the subject of the week? It usually says in the heading of the rant feed, but now there's just the news about the issue tracker.

After years of using an android wear on a regular basis I've gotten used to it, I use pujie black for a simplistic watch face and love it, I answer calls on it (although it doesn't have a speaker), and reading texts has been a lifesaver at times. I initially had an issue with the battery life but that was probably my fault for creating a really animation heavy watch face on watchmaker. Anyways while I love the thing it's really excessive (i know original argument huh?), I would love a smart band that can do all the simple things ( tell time make calls and display/read notifications ) and some awesome IoT remote functionality. After some research I found the nex band (I had actually seen this band often prior on Amazon but always just skipped over it cause I assumed that it was a fitness tracker, lesson learned again, don't assume). It looked promising, unfortunately it lacked a few key points that are essential to me. It was missing the most obvious thing, a clock, the band is split up into 4-5 rgb displays so there isn't much room for a clock. Second there is a proprietary clip on micro usb adapter (Ughhhhhh). Finally it it looks too niche and bulky. I'm keeping an eye on it cause i would love it if they at least fixed the clock and appearance issue as I don't travel much so the adapter would just sit on my nightstand anyways. Does anyone know of anything similar to the nex, everytime I search anywhere I get nothing but fitness or motion trackers.