The mobile web version of GitHub is absolute garbage. It's so shitty I don't even get why they bother. It lacks basic features like issue searching and the interface is so dumbed down everything just feels cheap and I always feel like I'm missing out.

All the devs I've talked to say they always just select "show desktop version." I do that too. It works perfectly. It's so fucking annoying. I wish they would just make a real mobile version, that's not missing features, or just default to the desktop app on mobile - works fine and everyone uses it anyway.

Its Friday, you all know what that means! ... Its results day for practiseSafeHex's most incompetent co-worker!!!

*audience: wwwwwwooooooooo!!!!*

We've had a bewildering array of candidates, lets remind ourselves:

- a psychopath that genuinely scared me a little
- a CEO I would take pleasure seeing in pain
- a pothead who mistook me for his drug dealer
- an unbelievable idiot
- an arrogant idiot obsessed with strings

Tough competition, but there can be only one ... *drum roll* ... the winner is ... none of them!

*audience: GASP!*
*audience member: what?*
*audience member: no way!*
*audience member: your fucking kidding me!*

Sir calm down! this is a day time show, no need for that ... let me explain, there is a winner ... but we've kept him till last and for a good reason

*audience: ooooohhhhh*

You see our final contestant and ultimate winner of this series is our good old friend "C", taking the letters of each of our previous contestants, that spells TRAGIC which is the only word to explain C.

*audience: laughs*

Oh I assure you its no laughing matter. C was with us for 6 whole months ... 6 excruciatingly painful months.

Backstory:

We needed someone with frontend, backend and experience with IoT devices, or raspberry PI's. We didn't think we'd get it all, but in walked an interviewee with web development experience, a tiny bit of Angular and his masters project was building a robot device that would change LED's depending on your facial expressions. PERFECT!!!

... oh to have a time machine

Working with C:

- He never actually did the tutorials I first set him on for Node.js and Angular 2+ because they were "too boring". I didn't find this out until some time later.

- The first project I had him work on was a small dashboard and backend, but he decided to use Angular 1 and a different database than what we were using because "for me, these are easier".

- He called that project done without testing / deploying it in the cloud, despite that being part of the ticket, because he didn't know how. Rather than tell or ask anyone ... he just didn't do it and moved on.

- As part of his first tech review I had to explain to him why he should be using if / else, rather than just if's.

- Despite his past experience building server applications and dashboards (4 years!), he never heard of a websocket, and it took a considerable amount of time to explain.

- When he used a node module to open a server socket, he sat staring at me like a deer caught in headlights completely unaware of how to use / test it was working. I again had to explain it and ultimately test it for him with a command line client.

- He didn't understand the need to leave logging inside an application to report errors. Because he used to ... I shit you not ... drive to his customers, plug into their server and debug their application using a debugger.

... props for using a debugger, but fuck me.

- Once, after an entire 2 days of tapping me on the shoulder every 15 mins for questions / issues, I had to stop and ask:

Me: "Have you googled it?"
C: "... eh, no"
Me: "can I ask why?"
C: "well, for me, I only google for something I don't know"
Me: "... well do you know what this error message means?"
C: "ah good point, i'll try this time"

... maybe he was A's stoner buddy?

- He burned through our free cloud usage allowance for a month, after 1 day, meaning he couldn't test anything else under his account. He left an application running, broadcasting a lot of data. Turns out the on / off button on the dashboard only worked for "on". He had been killing his terminal locally and didn't know how to "ctrl + c a cloud app" ... so left it running. His intention was to restart the app every time you are done using it ... but forgot.

- His issue with the previous one ... not any of his countless mistakes, not the lack of even trying to make the button work, no, no, not for C. C's issue is the cloud is "shit" for giving us such little allowances. (for the record in a month I had never used more than 5%).

- I had to explain environment variables and why they are necessary for passwords and tokens etc. He didn't know it wasn't ok to commit these into GitHub.

- At his project meetups with partners I had to repeatedly ask him to stop googling gifs and pay attention to the talks.

- He complained that we don't have 3 hour lunch breaks like his last place.

- He once copied and pasted the same function 450 times into a file as a load test ... are loops too mainstream nowadays?

You see C is our winner, because after 6 painful months (companies internal process / requirements) he actually achieved nothing. I really mean that, nothing. Every thing was so broken, so insecure / wide open, built without any kind of common sense or standards I had to delete it all and start again ... it took me 2 weeks.

I hope you've all enjoyed this series and will join me in praying for the return of my sanity ... I do miss it a lot.

Yours truly,
practiseSafeHex

Me: *Opens GitHub issue*

Maintainer: "it's a known issue"

# issue closed

> installs devRant app on my iPhone
> too lazy to type my 18-char random password on mobile
> password manager app not on App Store yet
> dig up my old Macbook
> install XCode & homebrew package manager
> install 2 other package managers using homebrew
> install App deps from the 2 package managers
> query stackoverflow for why my deps fail to install
> open App in XCode
> setup Apple provisioning profile
> trust my certificate on my iPhone
> dig up an old router & setup a local WiFi network
> start a server on my laptop to serve my PGP keys
> download my PGP keys to my iPhone
> app crashes
> open an issue on github with steps to reproduce & stacktrace
...
> type my 18-char random password
> rant on how I wasted an entire afternoon

The funniest Github issue log I've seen, and probably will ever see...

someone was doing this on github issue feed. I mean what the heck dude, this is going out of hand.

I hate ZenHub. For those who haven't heard of it, it's an agile project management solution that is hacked (and by hacked I mean really hacked) on top of Github.

It's touted as being convenient because you can have all your issues in Github and then look at them in epics and board format. Sounds awesome. Except it's not. For everything "convenient" it does, it severely lacks the most basic ticket management features that make any ticket management solution usable. Ex., you can't copy tickets. That's right - if you're creating 20 similar tickets, which I've needed to do in the past, you must create each one individually. New ticket -> add labels -> add assignee -> add title -> add description and then submit. 20 times.

ZenHub is so bad and so poorly conceived that many of those who use it have lost sight of project management reality and are blind to the 300 other PM products out there that are better.

True story: a couple of weeks ago people were celebrating because ZenHub added functionality to allow you to define what epic an issue belonged in while you were creating it. For those who aren't familiar with what that means, let me explain: before two weeks ago, when creating an issue in ZenHub, to fill out this "epic" field, you needed to first create the issue and then edit it to fill in the epic.

Let me break that down in devRant terms: it's the equivalent of not being able to add tags to a rant until you create it and then go back and edit it. Complete lunacy is the only way to describe it. And when they added the functionality two weeks ago allowing you to do it all in one step, people praised them!!!

Yeah, ZenHub sucks.

Did you solve the issue?

My only issue with Microsoft buying Github is that it's one more step towards full almighty power for the tech giants. Soon everything will be Microsoft, or Google, or Facebook. It'll be like in Demolition Man, where every restaurant is Taco Bell/Pizza Hut.

1% of OSS: “I came across this very common issue which is a pain in the arse, I pulled together this awesome solution for the community, packaged it nicely, here, use it.” - 3 ⭐️ on Github.

The remaining 99%: “I was bored last Sunday so maed zis.” - 10’393 ⭐️ on GitHub.

Me: *Gets an error message I don't recognize.* fuck.

Me: *Googles error*
*First result is not StackOverflow but a github issue instead* oh FUCK!

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.

A user opened an issue on Github saying something doesn't compile. Fair enough, it didn't.

Another user comments saying "I have the exact same issue but after the program launches"

Bitch no, that's not the same issue. Not at all.

!rant

Yesterday I upgraded VS Code (insiders version, i.e daily/beta/etc) to the latest version and ran into a minor bug. I reported an issue in the Github repository, and 40 minutes later got a reply saying It was fixed and I can upgrade to the newest version.

Kudos on Microsoft and the VS Code team!

Had an interesting time these past few days. Had a customer who, when I left for vacay, was complaining that he couldn't get access to our private package registry. Get back, this issue is still active.

We'd granted access to his github enterprise, and for some reason he wasn't getting the activation email. We spent about 22 hours of customer support time on his failing to help himself before he finally escalated to the standard 40 person IT enterprise tantrum/come to jesus meeting.

Long story short, he had somehow ignored repeated attempts (35 email replies to the ticket chain, 4 phone calls) to get him to check his spam folder. In which, as it was revealed to all the hollywood squares in attendance, there were no less than 35 activation emails from github granting him access. Of course, none of this was his fault. And while screensharing his big brain to god and everyone he decides the problem is now actually Microsoft because their office 365 spam email filtered his emails incorrectly. We of course agreed with his big brain, smoothed over his bruised ego and went about our day.

I mean, fair enough, it's kind of dumb that Microsoft ever spam lists github, but still. I was just a fly on the wall, and he burned all his paid support tickets on the issue, so hopefully we won't be dealing with him again this year.

Also, this is an edge case with our new product line, most of our customers are painless.

A repo on GitHub I'm maintaining has grown with 200k downloads / month since I started working on it a year ago. My recipe? I added an npm badge in the readme showing downloads / month and I responded to every issue and reviewed every PR. Now there's so much issues and PRs coming in that we had to add an extra maintainer, feels great! Teamwork, fuck yeah!

Not every PR got merged of course, but every single one of them got reviewed. Just being a good and friendly developer, giving back to the community that has given me so much. Some tips for you maintainers out there. If you have a popular project and no time there's always someone else who's willing to spend time on it, ask around and you will surely find someone else.

This just in everyone...

Android Dev: *sent and email to network admin* can you please unblock github for a few mins.

Network admin: *Replied* Can you take a screenshot whats the error your getting.

Android Dev: *Replied with screenshot* "Failed to load resource: the server responded with a status of 503 (Service Unavailable)"

Network admin: that is a known issue. *Replied with Wordpress Links.

Android Dev: why is github working outside our network then?

Network admin: there must be a problem with your code that needs to be tweaked.

Team: *FACE PALM*

When people post non-issues on GitHub issues 😡

Issue: "How do I...?"
Issue: "Nevermind, figured it out!"
Issue: Closed.

HOD: Hey, Can you conduct web development workshop for Jr.'s?

Me: no issue, Can you share syllabus?

HOD: download from the internet.

Me: cool, So may also be trained them related to GitHub.

HOD: what is GitHub?

Me: -_- nothing its little thing, I will manage.

It's more than a story bear with me.
Open source world is big enough to scare a beginner like me, which happened when I started with my first contribution in the year 2015. So many platforms, lot of organisations, freaking images of coding languages, pull request, issues and bugs- these all were enough to freak me out.

The only thing which motivated me to stay and know about the open source technology was to develop my first program using python. I was in great difficulty as when I started writing my program I was stuck after almost every two to three stages of compilation, so I needed guidance. I started my search on Github by creating my repository, pushing my code and following developers. I was amazed to see such a good response from people around me, not only they helped me to debug and fix the issue but they also helped me to understand and build my program from a new perspective. Daily discussions and communication, new issue build up and solving them by the traditional way of GUI further motivated me to learn the Git using the command line tool.

I still remember the year I worked on a repo using the command line tool, it was amazing. Within months or few, the fear of open source tools, community, interaction all just flew away. With this rant I will like to suggest all the beginners and open source enthusiast to just step a foot ahead and ask openly to the world- "I need help" and believe me you will be showered with information and help from all the world.

Happy contribution.

Let the student use their own laptops. Even buy them one instead of having computers on site that no one uses for coding but only for some multiple choice tests and to browse Facebook.

Teach them 10 finger typing. (Don't be too strict and allow for personal preferences.)

Teach them text navigation and editing shortcuts. They should be able to scroll per page, jump to the beginning or end of the line or jump word by word. (I am not talking vi bindings or emacs magic.) And no, key repeat is an antifeature.

Teach them VCS before their first group assignment. Let's be honest, VCS means git nowadays. Yet teach them git != GitHub.

Teach git through the command line. They are allowed to use a gui once they aren't afraid to resolve a merge conflict or to rebase their feature branch against master. Just committing and pushing is not enough.

Teach them test-driven development ASAP. You can even give them assignments with a codebase of failing tests and their job is to make them pass in the beginning. Later require them to write tests themselves.

Don't teach the language, teach concepts. (No, if else and for loops aren't concepts you god-damn amateur! That's just syntax!)

When teaching object oriented programming, I'd smack you if do inane examples with vehicles, cars, bikes and a Mercedes Benz. Or animal, cat and dog for that matter. (I came from a self-taught imperative background. Those examples obfuscate more than they help.) Also, inheritance is overrated in oop teachings.

Functional programming concepts should be taught earlier as its concepts of avoiding side effects and pure functions can benefit even oop code bases. (Also great way to introduce testing, as pure functions take certain inputs and produce one output.)

Focus on one language in the beginning, it need not be Java, but don't confuse students with Java, Python and Ruby in their first year. (Bonus point if the language supports both oop and functional programming.)

And for the love of gawd: let them have a strictly typed language. Why would you teach with JavaScript!?

Use industry standards. Notepad, atom and eclipse might be open source and free; yet JetBrains community editions still best them.

For grades, don't your dare demand for them to write code on paper. (Pseudocode is fine.)

Don't let your students play compiler in their heads. It's not their job to know exactly what exception will be thrown by your contrived example. That's the compilers job to complain about. Rather teach them how to find solutions to these errors.

Teach them advanced google searches.

Teach them how to write a issue for a library on GitHub and similar sites.

Teach them how to ask a good stackoverflow question :>

So this is how I met my girl on github.
I wanted to built something like a media center, primary for music, but using YouTube as source. I started looking for a lib. Found a broken one. Opened an issue but got a comment: "Can't fix because, you get ... [read more]

me and my co-workers: "lmao lets see if this github copilot is so great as they claim"

copilot: *solves issue we've been working on for 8 hours, in 10 seconds*

me and my co-workers:
(┛ಠ_ಠ)┛彡┻━┻

That feeling when you have been finding what is wrong for hours just to find that your problem is also an unresolved issue on github

Comment on a GitHub issue on one of my repos:

"Almond I posted this feature request last month, please start to work on it in your free time"

Dude, that's just made it a whole lot less likely I'll even give that feature request the time of day. Take your entitled arse attitude to the bank and pay me to do it if you care that much.

Also, free time?!?! Hahahaha.

What an absolute fucking disaster of a day. Strap in, folks; it's time for a bumpy ride!

I got a whole hour of work done today. The first hour of my morning because I went to work a bit early. Then people started complaining about Jenkins jobs failing on that one Jenkins server our team has been wanting to decom for two years but management won't let us force people to move to new servers. It's a single server with over four thousand projects, some of which run massive data processing jobs that last DAYS. The server was originally set up by people who have since quit, of course, and left it behind for my team to adopt with zero documentation.

Anyway, the 500GB disk is 100% full. The memory (all 64GB of it) is fully consumed by stuck jobs. We can't track down large old files to delete because du chokes on the workspace folder with thousands of subfolders with no Ram to spare. We decide to basically take a hacksaw to it, deleting the workspace for every job not currently in progress. This of course fucked up some really poorly-designed pipelines that relied on workspaces persisting between jobs, so we had to deal with complaints about that as well.

So we get the Jenkins server up and running again just in time for AWS to have a major incident affecting EC2 instance provisioning in our primary region. People keep bugging me to fix it, I keep telling them that it's Amazon's problem to solve, they wait a few minutes and ask me to fix it again. Emails flying back and forth until that was done.

Lunch time already. But the fun isn't over yet!

I get back to my desk to find out that new hires or people who got new Mac laptops recently can't even install our toolchain, because management has started handing out M1 Macs without telling us and all our tools are compiled solely for x86_64. That took some troubleshooting to even figure out what the problem was because the only error people got from homebrew was that the formula was empty when it clearly wasn't.

After figuring out that problem (but not fully solving it yet), one team starts complaining to us about a Github problem because we manage the github org. Except it's not a github problem and I already knew this because they are a Problem Team that uses some technical authoring software with Git integration but they only have even the barest understanding of what Git actually does. Turns out it's a Git problem. An update for Git was pushed out recently that patches a big bad vulnerability and the way it was patched causes problems because they're using Git wrong (multiple users accessing the same local repo on a samba share). It's a huge vulnerability so my entire conversation with them went sort of like:

"Please don't."
"We have to."
"Fine, here's a workaround, this will allow arbitrary code execution by anyone with physical or virtual access to this computer that you have sitting in an unlocked office somewhere."
"How do I run a Git command I don't use Git."

So that dealt with, I start taking a look at our toolchain, trying to figure out if I can easily just cross-compile it to arm64 for the M1 macbooks or if it will be a more involved fix. And I find all kinds of horrendous shit left behind by the people who wrote the tools that, naturally, they left for us to adopt when they quit over a year ago. I'm talking entire functions in a tool used by hundreds of people that were put in as a joke, poorly documented functions I am still trying to puzzle out, and exactly zero comments in the code and abbreviated function names like "gars", "snh", and "jgajawwawstai".

While I'm looking into that, the person from our team who is responsible for incident communication finally gets the AWS EC2 provisioning issue reported to IT Operations, who sent out an alert to affected users that should have gone out hours earlier.

Meanwhile, according to the health dashboard in AWS, the issue had already been resolved three hours before the communication went out and the ticket remains open at this moment, as far as I know.

Someone here linked the Gordon repository a couple of days ago and I made 3 issues on it.
Dev replied:

Alright so listen to this. I was working on a project, it was a fork of another github repo. So the project is mainly based in PHP, simple enough right?

Anyways I have my version working and I put it up as a website and am doing fairly well with it. I was trying to advertise it a bit on reddit ( pay attention to the trying ) then someone comes along and asks how I made it and all that.

Just trying to be kind I tell them what I used and all that to make it. Then they come back a few hours later explaining that they are trying to make their own version for "fun". Then they proceed to explain that they are having some issues with it, it obviously is something in the back-end (they must've fucked up something).

So I politely ask them to show me the code so I can help them fix it.

He refuses.

So we exchanged a bit. What his excuse for not showing me his code ( Keep in mind he is also taking this from an open-source software same as me he has simply broken something and can't fix it himself ) is he doesn't want me stealing his ideas...

I nearly snapped when he did that, I had already seen the site he made, from that end it wasn't anymore spectacular than mine and no serious changes seemed to have occurred. The best part is that it was broken. He asked for my help and refused to let me see the code so I told him that I simply couldn't help him fix it then. He goes and is just going alright.

Next he then asks me how I solved this issue and that issue and he wanted the code that I used to fix each of these little issues. Pretty much to the point that it would've been a clone of my site. So I just didn't give him anything.

Didn't hear from him for a few hours, next thing I know he messages me asking if he can fix my site so it is mobile friendly...First off my site is mobile friendly and works pretty well. I have been spending a lot more quality time to work on this than him.

Moral of the story is, some people are retards.

The wtf moment on GitHub when you are only trying to suggest something and they assign the whole issue to you.

funny out of context...

Issue on the original Apollo 11 AGC source code

My girlfriend said I have no commitment, I showed her how green my GitHub profile is.
I don't understand understand why she ain't replying my texts.
I'll create an issue.

You know what grinds my gears?

Those people who ask about a problem on stackoverflow, github issue, or other sites and then reply:

"Never mind, found the problem!", Without telling what was the problem and did they fix it.

Fuck those people.*

*Not literally.

Follow up to yesterday’s “hybrid/cross-platform is shit” rant about Electron apps being blocked from the Apple App Store.

See the below image of the github issues template on the Electron repo, to file an issue for this problem.

Yes, this is such a common issue with their product, they’ve made it easier to file a github issue. Let’s not address the fact that there is a fundamental flaw in the approach they are using, let’s just make it easier to open a ticket while everyone waits to see if we are allowed to ship our app.

I’ve also heard talk that under some circumstances it’s possible for them to patch out the libraries causing issues. Apple provides tools to identify these libraries ... therefore Electron is doing fuck all to adresss this issue, and adopting a “wait until someone complains” style of approach.

A+

Search an issue on Google, find a cool GitHub project, try it out.

Search an issue with the new project, find another cool GitHub...

The GitHub Circle.

Ah, my first issue!

I was hopelessly lost in a problem when I found an Issue on Github describing the exact same problem.
Unfortunately, the message board it didn't quite help me solving the problem.
Some time later I managed to solve the problem, and remembering the Github issue, I wanted to post an actually helpful message.

Oh but wait. The issue was fucking closed.

When you see what worked for someone else with a similar issue on GitHub and run it.

Trust me, I hope I know what I'm doing too.

I fucking hate chained methods. Ok, not all of them. Query things like array.where.first... that stuff is ok.

Specially if it's part of the std lib of a lang, which would be probably written by a very competent coder and under scrutiny.
But if you're not that person, chances are you'll produce VASTLY inferior code.

I'm talking about things like:
expect(n).to.be(x).and.not(y)

And the reason I don't like it is because it's all fine and dandy at first.

But once you get to the corner cases, jesus christ, prepare to read some docpages.

You end up reading their entire fucking docs (which are suboptimal sometimes) trying to figure if this fucking dsl can do what you need.

Then you give up and ask in a github issue. And the dev first condescends you and then tells you that the beautiful eden of code he created doesn't let you do what you want.

The corner cases usually involve nesting or some very specific condition, albeit reasonable.

This kind of design is usually present in testing or validation js libraries. And I hate all of those for it.

If you want a modern js testing lib that doesn't suck ass, check avajs. It's as simple as testing should be.

No magic globals, no chaining, zero config. Fuck globals forced by libs.

But my favorite thing about it that is I can put a breakpoint wherever the fuck I want and the debugger stops right fucking there.

Code is basically lines of statements, that's it, and by overusing chaining, by encouraging the grouping of dozens of statements into one, you are preventing me from controlling these statements on MY code.

As an end dev, I only expect complexity increases to come from the problems themselves rather than from needlessly "beautified" apis.

When people create their own shitty dsl, an image comes to my mind of an incoherent rambling man that likes poetry a lot and creates his own martial art, which looks pretty but will get your ass kicked against the most basic styles of fighting.

I fucking hate esoteric code.

Even if I had to execute a list of functions, I'd rather send them in an array instead of being able to chain them because:
a) tree shaking would spare from all the functions i didn't import
b) that's what fucking arrays are for, to contain several things.

This bad style of coding is a result of how low the barrier to code in higher level langs are.

As a language or library gets easier to use you might think that's a positive thing. But at the same time it breeds laziness.

Js has such a low learning curve that it attacts the wrong kind of devs, the lazy, the uninspired, the medium.com reader, the "i just care about my paycheck" ones.

Someone might think that by bashing bad js devs I'm trying to elevate myself.

That'd be extremely stupid. That's like beating a retarded blind man in a game and then saying "look, I'm way better than this retarded blind man".

I'm not on a risky point of view, just take a stroll down npmjs.com. That place is a landfill. Not really npm's fault, in fact their search algorithm is good.

It's just the community.

Every lang has a ratio of competence. Of competent to incompetent devs.

You have the lang devs and most intelligent lib devs at the top. At the bottom you have the bottom.

Well js has a horrible ratio. I wouldn't be shocked to find out that most js devs still consider using import or await the future.

You could say that js improved a lot, that it was way worse beforr. But I hate chaining now, and i hated back then!

On top of this, you have these blog web companies, sucking the "js tutorial" business tit dry, pumping out the most obscenely unprofessional and bar lowering tutorials you can imagine, further capping the average intelligence of most js devs.

And abusing SEO while they're at it, littering the entire web with copy paste content.

.NET drinking game:
* Drink every time IntelliSense refuses to tell you what the actual error is because it's too busy choking on lambda syntax from a decade ago
* Take a shot every time you discover a closed, unresolved Github issue discussing your current showstopping build/CI problem
* Finish your drink every time the solution to your problem involves either manual edits to your CSPROJ (or whatever) file, or creating a new project altogether and copying all your fucking files over

Not sure if this has been posted before but GitHub has an official dark mode now!

And it's pretty beautiful too
(Especially check out how your own comments look on an issue!)

I use a library and it gives me some strange error message. No problemo, just file an issue on GitHub asking the maintainer if I'm plain stupid or the lib actually has a flaw. As it was a question, I have not posted a dump and all the shit.
Maintainer responds with a snarky comment about his crystal ball being broken and I have to submit a log, a dump, debug information and a bunch of other stuff.
Well, what choice do I have, I collect all the requested information, create a wall of text comment, all nicely formatted.
And the issue ends here. Myths say, the maintainer got asked to join Elvis on Mars.

I mean, why do you ask all the shit from me in a unprofessional manner just to stop answering? Just say "I have no clue why it behaves like this" and I know whats playin. But that's just ... sad.

*landing page: "state of the art". "look how many companies use this"
*6 months later: have some problems. discover github open issue that it can go into an unrecoverable state and every commenter migrated to competitor.

How I got selected for GSoC'19:
I will describe my journey from detail i.e from the 1st year of the college. I joined my college back in 2017 (July), I was not even aware of Computer Science. What are the different languages of CS, but I had a strong intuition of doing BTech from CSE only?

So yeah I was totally unaware of the computer science stuff, but I had a strong desire to learn it and I literally don’t know why I had this desire. After getting into college, I was learning HTML, Python, and C, also I am really thankful to my friends who really helped me to learn, building logic and making stuff out of it. During the 1st month of joining the college, I got to know what is Open Source, GSoC, Github due to my helpful seniors. But I was not into Open Source during my 1st year of college as I thought it is very difficult to start. In my 1st year, I used to do competitive programming and writing scripts in Python to automate various stuff. I never thought that I would even start doing Open Source development, also in the summer vacations after the 1st year I used to practice programming on HackerRank and learnt an awesome course called Automate the Boring Stuff with Python(which I think is one of the most popular courses for Python) which really helped me to build by Python skills.

Now the 2nd year came, I was totally confused between doing Open Source development or continue with my Competitive programming. But I wanted to know about Open Source development, so I thought to start now will be a good idea. I started attending meetups of OSDC(Open Source Developers Club) which is a hub of my college, which really helped me to know more about Open Source development from my seniors. I started looking for beginner friendly projects in Python on the website Up For Grabs, it’s really helpful for the beginners. So I contributed in a few of them, and in starting it was really tough for me but yeah I continued, which really helped me to at least dive into Open Source. Now I thought to start contributing in any bigger project, which has millions of lines of code which will be really interesting. So I started looking for the project, as I was into web development those days so I thought to find a project which matches my domain. So yeah I finally landed on Oppia:
Oppia

I started contributing into Oppia in November, so yeah in starting it was really difficult for me to solve any issue (as I wasn’t aware of the codebase which was really big), but yeah mentors at Oppia are really helpful, they guided me which really helped me to start my journey with Oppia. By starting of January I was able to resolve around 3–4 issues, which helped me to become the collaborator at Oppia, afterward I really liked contributing to it and I was able to resolve around 9–10 issues by the end of February, which landed me to become a Team Member at Oppia which was really a confidence boost and indication for me that I am in the right direction.

Also in February, the GSoC organizations list was out, and yeah Oppia was also participating in it. The project ideas of Oppia were really interesting, I became even confused to pick anyone because there were 4–5 ideas which seemed interesting to me. After 1–2 days of thought process I decided to go for one of them, i.e “Asking students why they picked a particular answer”, a full stack project.

I started making proposals on it, from the first week of March. I used to get my proposal reviewed frequently from the mentors, which really helped me to build a good and strong proposal.

I must say a well-defined proposal is the most important key for getting selected in GSoC, also you must have done some contributions to the organization earlier which I think really maximize your chances of selection in GSoC.

So after my proposal was made, I submitted it on the GSoC website.
Result Day:

It was the result day, by the way, I had the confidence of being selected, but yeah I was a little bit nervous. All my friends were asking when is your result coming, I told them it will come at 12.30AM (IST). Finally, the time came when I refreshed the GSoC website, Voila the results were out. I opened the Oppia organization page, and yeah my name was there. That was the day I was really happy and satisfied, I was thinking like I have achieved something in my life. It was a moment of pleasure for me, I called my parents and told them my result, they were really happy for me.

I say cracking GSoC is worth it, the preparation you do, the contributions you do, the making of the proposal is really worth.

I got so many messages from my juniors, friends, and seniors, they congratulated me. After that when I uploaded my result of Facebook and LinkedIn, there were tons of comments and likes on the post. So yeah that’s my journey.

By the way, I am writing this post after really late, sorry for it. I must have done it earlier, but due to milestone 1 of GSoC, I was busy.

I got a dayjob in a company. I got an error. I cannot solve it and I am so desperate. So I go to stackoverflow, nobody answers. I post on git issue, but nobody solves the problem. So, I pay someone to solve it, like Hackhands.com to find a mentor. There is no mentor that can help. So I pay more, hired a peer, and finally a development team just to help me. They get paid only if they solved it.

But each of my folks repeat my same steps, asking on stackoverflows or github, and none of these help. So, they end up hiring their own friends and mentors. Their friends also end up paying (pay before problem solved) someone to help them.

their friends pay for friends of friends, then friends of friends of friends

And all of a sudden it becomes a giant MLM scheme.

And those people they paid for actually work for a company behind the scene which I am a founder of 😁

Multi billions startup idea, is it?

Regarding Article 13 (or 17 or wherever it moved to now)… Let's say that the UK politicians decide to be dicks and approve the law. After that, we need to get it engineered in, right? Let's talk a bit about how.. well, I'd maybe go over it. Been thinking about it a bit in the shower earlier, so.. yeah.

So, fancy image recognition or text recognition from articles scattered all over the internet, I think we can all agree.. that's infeasible. Even more so, during this lobby with GitHub and OpenForum Europe, guy from GitHub actually made a very valid point. Now for starters, copyright infringement isn't an issue on the platform GitHub that pretty much breathes collaboration. But in the case of I-Boot for example, that thing from Apple that got leaked earlier. If that would get preemptively blocked.. well there's no public source code for it to get compared against to begin with, right? So it's not just "scattered all over the internet, good luck crawling it", it's nowhere to be found *at all*.

So content filtering.. yeah. Nope, ain't gonna happen. Keep trying with that, EU politicians.

But let's say that I am a content creator who hates the cancer of joke/meme because more often than not it manifests itself as a clone of r/programmerhumor.. someone decides to freeboot my content. So I go out, look for it, find it. Facebook and the likes, make it easier to find it in the first place, you dicks. It's extremely hard to find your content there.

So Facebook implements a way to find that content a bit easier maybe. Me being the content creator finds it.. oh blimey! It can't be.. it's the king of freebooting on Facebook, SoFlo! Who would've thought?! So at that point.. I'd like to get it removed of course. Report it as copyright infringement? Of course. Again Facebook you dicks, don't make it so tedious to fill in that bloody report. And look into it quickly! The videos those SoFlo dicks post is only relevant in the first 48h or so. That's where they make the most money. So act more quickly.

So the report is filled, video's taken down.. what else? Maybe temporarily make them unable to post as a bit of a punishment so that they won't do it again? And put in a limit to the amount of reports they can receive. Finally, maybe reroute the revenue stream to the original content creator instead. That way stolen content suddenly becomes free exposure! Awesome!

*suddenly realizes that I've been talking about the YouTube copyright strike system all along*

… Well.. maybe something like that then? That shouldn't be too hard to implement, and on YouTube at least it seems to be quite effective. Just imagine SoFlo and the likes that are repeat offenders, every 3 posts they get their account and page shut down. Good luck growing an audience that way. And good luck making new accounts all the time to start with.. account verification technology is pretty good these days. Speaking of experience here, tried bypassing Facebook's signup hoops a fair bit and learned a bit about some of the things they have red flags on, hehe.

But yeah, something like that maybe for social media in general. And.. let's face it, the biggest one that would get hurt by something like this would be Facebook. And personally I think it's about time for that bastard company to get a couple of blows already.

What are your thoughts on this?

How people chat with their girlfriend-

BOYS - chat on WhatsApp

Men - calls directly on phone

Programmers -Raise an Issue & comment on GitHub😂😜

Yesterday my docker build started failing for my .NET core project, but it worked on Windows!

Today I found a Github issue, 4 hours old, what fixes it? Downgrading my kernel, which I upgraded a few days ago to v5

I would never have discovered that on my own, what the hell

I opened an issue on a repo telling the owner that placing a "test passing" badge on the readme but not having other tests than an "ExampleTest" and no tests of the actual functionality is bad practice and what he thinks about updating the readme.

The result was a deletion (not close) of the issue and a ban from contributing (issues, PRs) on any of his projects.

And it was not some small "ten persons use this" project but a large boilerplate project with 2.4k github stars and over 800 forks. You would expect a little bit more professionalism of someone with that popularity.

Hey GitHub Idiot No Need To Write Capitalized Issue Requests Like This It Makes You Look Incompetent We Are Not Working In .NET Here On GitHub

just absolute 🤡

GitHub issue comment:
"problem solved by applying a patch"

WHAT FUCKING PATCH DAMNIT!

Github 101 (many of these things pertain to other places, but Github is what I'll focus on)

- Even the best still get their shit closed - PRs, issues, whatever. It's a part of the process; learn from it and move on.

- Not every maintainer is nice. Not every maintainer wants X feature. Not every maintainer will give you the time of day. You will never change this, so don't take it personally.

- Asking questions is okay. The trackers aren't just for bug reports/feature requests/PRs. Some maintainers will point you toward StackOverflow but that's usually code for "I don't have time to help you", not "you did something wrong".

- If you open an issue (or ask a question) and it receives a response and then it's closed, don't be upset - that's just how that works. An open issue means something actionable can still happen. If your question has been answered or issue has been resolved, the issue being closed helps maintainers keep things un-cluttered. It's not a middle finger to the face.

- Further, on especially noisy or popular repositories, locking the issue might happen when it's closed. Again, while it might feel like it, it's not a middle finger. It just prevents certain types of wrongdoing from the less... courteous or common-sense-having users.

- Never assume anything about who you're talking to, ever. Even recently, I made this mistake when correcting someone about calling what I thought was "powerpc" just "power". I told them "hey, it's called powerpc by the way" and they (kindly) let me know it's "power" and why, and also that they're on the Power team. Needless to say, they had the authority in that situation. Some people aren't as nice, but the best way to avoid heated discussion is....

- ... don't assume malice. Often I've come across what I perceived to be a rude or pushy comment. Sometimes, it feels as though the person is demanding something. As a native English speaker, I naturally tried to read between the lines as English speakers love to tuck away hidden meanings and emotions into finely crafted sentences. However, in many cases, it turns out that the other person didn't speak English well enough at all and that the easiest and most accurate way for them to convey something was bluntly and directly in English (since, of course, that's the easiest way). Cultures differ, priorities differ, patience tolerances differ. We're all people after all - so don't assume someone is being mean or is trying to start a fight. Insinuating such might actually make things worse.

- Please, PLEASE, search issues first before you open a new one. Explaining why one of my packages will not be re-written as an ESM module is almost muscle memory at this point.

- If you put in the effort, so will I (as a maintainer). Oftentimes, when you're opening an issue on a repository, the owner hasn't looked at the code in a while. If you give them a lot of hints as to how to solve a problem or answer your question, you're going to make them super, duper happy. Provide stack traces, reproduction cases, links to the source code - even open a PR if you can. I can respond to issues and approve PRs from anywhere, but can't always investigate an issue on a computer as readily. This is especially true when filing bugs - if you don't help me solve it, it simply won't be solved.

- [warning: controversial] Emojis dillute your content. It's not often I see it, but sometimes I see someone use emojis every few words to "accent" the word before it. It's annoying, counterproductive, and makes you look like an idiot. It also makes me want to help you way less.

- Github's code search is awful. If you're really looking for something, clone (--depth=1) the repository into /tmp or something and [rip]grep it yourself. Believe me, it will save you time looking for things that clearly exist but don't show up in the search results (or is buried behind an ocean of test files).

- Thanking a maintainer goes a very long way in making connections, especially when you're interacting somewhat heavily with a repository. It almost never happens and having talked with several very famous OSSers about this in the past it really makes our week when it happens. If you ever feel as though you're being noisy or anxious about interacting with a repository, remember that ending your comment with a quick "btw thanks for a cool repo, it's really helpful" always sets things off on a Good Note.

- If you open an issue or a PR, don't close it if it doesn't receive attention. It's really annoying, causes ambiguity in licensing, and doesn't solve anything. It also makes you look overdramatic. OSS is by and large supported by peoples' free time. Life gets in the way a LOT, especially right now, so it's not unusual for an issue (or even a PR) to go untouched for a few weeks, months, or (in some cases) a year or so. If it's urgent, fork :)

I'll leave it at that. I hear about a lot of people too anxious to contribute or interact on Github, but it really isn't so bad!

Things that piss me off in github issue comments:

- "halp it doesn't work!!!" no description, no steps to reproduce, nothing.

- people writing comments in a random ass language that nobody understands so everybody except them has to go through the effort of translating it.

- issue comments that escalate into a meme fest because the issue was linked on reddit or some other platform

If Schrödinger submitted his cat experiment as a GitHub issue, what label would it get?

"can't reproduce".

Man, contributing to open source projects seems very intimidating to me.

I have never contributed to one of those repos on Github with a shit-ton of stars and a load of watchers. Made up my mind to start sometime around the start of September. Looked up a repo that I was very excited to contribute to. Went through their really large codebase, tried to understand as much as I could (They have a fair amount of documentation, but I just can't understand a lot of design decisions that were taken). Looked up one of the open issues marked for newbies, went through the relevant code to understand where and how I would have to make my changes in the code, and was about to start... when a seasoned contributor submitted a pull request.

This same occurrence has repeated itself 3 times now. If you mark an issue for beginners, maybe let the beginners handle them? Also, if you plan to contribute to an issue, why not announce your intention to do so? Get the issue assigned to you, so no one else ends up wasting their time coming up with a solution.

I would love to recommend this to the contributing team, but I am just way too scared to initiate a conversation with these guys. I mean, they are way more experienced and knowledgeable than me (some of them are even famous!).

I am definitely out of my depth with this project, and maybe should look for an easier one, but I really want to rise up to the challenge. Guess I'll stick around then, just waiting for my chance. :|

Choke on a fucking narwhals horn you pieces of shit, 28 days no ticket answer, then raised the issue again and again and again, still no answers, tried their email added in all github support readmes - got that in return, all their issues are closed except for the python wrapper, just fucking send me back a notice of your death already.

Returning from vacation tmr... But apparently we just had a "someone at github deleted all the repos and no backup"-like prod issue....

Well guess I say least can say "¯\_(ツ)_/¯ not my area, can't help u"

Right, that's fucking it. Enough. I'm all for learning new technologies, frameworks, and development protocols, but my time on this earth is limited and at the end of the day if I'm having to spend DAYS AND FUCKING DAYS just scouring through obscure forum posts because the documentation is shit and just hitting ONE FUCKING PROBLEM AFTER ANOTHER then there comes a point at which the time investment simply isn't worth it. I HATE throwing in the towel because some FUCKING CUNT code problem has got the better of me, but fucking sense must prevail here.

Laravel fucking Mix. Do any any of you use this shit on Windows? Because I take my fucking hat off to you. I'm done with it.

Oh, so your server uses 'public_html' instead of 'public' does it? Well, of course you can just set

mix.setPublicPath('public_html'); then can't you?

No, you can't. Why? Because fuck you, that's why. Not only do you have to hard-code your fucking public directory into each specified path, additionally you have to set

mix.setPublicPath('./');

Why? Because fuck you, that's why. It took me the best part of two days to discover that little nugget of information, buried at the bottom of some obscure corner of the internet in a random github issue thread. Fuck off.

Onto next problem. Another 5 hours invested to extract some patchy solution that I'm not at all happy with.

Rinse, repeat.

Make it work with BrowserSync by wrapping your assets like so:

<link rel="stylesheet" href="{{ mix('/build/css/main.css') }}">

Oh oh oh but "The Mix manifest does not exist"... despite a fresh install of Laravel 5.6 and all relevant node modules installed... follow some other random Github thread with a back and forth of time-consuming suggestions for avenues of experimentation, with no clear solution.

Er no, fuck off. I'm going back to Grunt and maybe I'll try Webpack/Mix in another year or two when there's actually some clear answers, but as it stands this a wild goose chase into a fucking black-hole and I've got better things to do with my precious time. Go die.

(long post is long)
This one is for the .net folks. After evaluating the technology top to bottom and even reimplementing several examples I commonly use for smoke testing new technology, I'm just going to call it:

Blazor is the next Silverlight.

It's just beyond the pale in terms of being architecturally flawed, and yet they're rushing it out as hard as possible to coincide with the .Net 5 rebranding silo extravaganza. We are officially entering round 3 of "sacrifice .Net on the altar of enterprise comfort." Get excited.

Since we've arrived here, I can only assume the Asp.net Ajax fiasco is far enough in the past that a new generation of devs doesn't recall its inherent catastrophic weaknesses. The architecture was this:

1. Create a component as a "WebUserControl"
2. Any time a bound DOM operation occurs from user interaction, send a payload back to the server
3. The server runs the code to process the event; it spits back more HTML

Some client-side js then dutifully updates the UI by unceremoniously stuffing the markup into an element's innerHTML property like so much sausage.

If you understand that, you've adequately understood how Blazor works. There's some optimization like signalR WebSockets for update streaming (the first and only time most blazor devs will ever use WebSockets, I even see developers claiming that they're "using SignalR, Idserver4, gRPC, etc." because the template seeds it for them. The hubris.), but that's the gist. The astute viewer will have noticed a few things here, including the disconnect between repaints, inability to blend update operations and transitions, and the potential for absolutely obliterative, connection-volatile, abusive transactional logic flying back and forth to the server. It's the bring out your dead approach to seeing how much of your IT budget is dedicated to paying for bandwidth and CPU time.

Blazor goes a step further in the server-side render scenario and sends every DOM event it binds to the server for processing. These include millisecond-scale events like scroll, which, at least according to GitHub issues, devs are quickly realizing requires debouncing, though they aren't quite sure how to accomplish that. Since this immediately becomes an issue with tickets saying things like, "scroll event crater server, Ugg need help! You said Blazorclub good. Ugg believe, Ugg wants reparations!" the team chooses a great answer to many problems for the wrong reasons:

gRPC

For those who aren't familiar, gRPC has a substantial amount of compression primarily courtesy of a rather excellent binary format developed by Google. Who needs the Quickie Mart, or indeed a sound markup delivery and view strategy when you can compress the shit out of the payload and ignore the problem. (Shhh, I hear you back there, no spoilers. What will happen when even that compression ceases to cut it, indeed). One might look at all this inductive-reasoning-as-development and ask themselves, "butwai?!" The reason is that the server-side story is just a way to buy time to flesh out the even more fundamentally broken browser-side story. To explain that, we need a little perspective.

The relationship between Microsoft and it's enterprise customers is your typical mutually abusive co-dependent relationship. Microsoft goes through phases of tacit disinterest, where it virtually ignores them. And rightly so, the enterprise customers tend to be weaksauce, mono-platform, mono-language types who come to work, collect a paycheck, and go home. They want to suckle on the teat of the vendor that enables them to get a plug and play experience for delivering their internal systems.

And that's fine. But it's also dull; it's the spouse that lets themselves go, it's the girlfriend in the distracted boyfriend meme. Those aren't the people who keep your platform relevant and competitive. For Microsoft, that crowd has always been the exploratory end of the developer community: alt.net, and more recently, the dotnet core community (StackOverflow 2020's most loved platform, for the haters). Alt.net seeded every competitive advantage the dotnet ecosystem has, and dotnet core capitalized on. Like DI? You're welcome. Are you enjoying MVC? Your gratitude is understood. Cool serializers, gRPC/protobuff, 1st class APIs, metadata-driven clients, code generation, micro ORMs, etc., etc., et al. Dear enterpriseur, you are fucking welcome.

Anyways, b2blazor. So, the front end (Blazor WebAssembly) story begins with the average enterprise FOMO. When enterprises get FOMO, they start to Karen/Kevin super hard, slinging around money, privilege, premiere support tickets, etc. until Microsoft, the distracted boyfriend, eventually turns back and says, "sorry babe, wut was that?" You know, shit like managers unironically looking at cloud reps and demanding to know if "you can handle our load!" Meanwhile, any actual engineer hides under the table facepalming and trying not to die from embarrassment.

1 - Spend 6 months building an app with Flutter
2 - Try to add in-app purchase. Must upload an apk to google console and register a product
3 - Must launch the app so the product is activated
4 - Console complains apk must contain 64 bits version
5 - Go to the issues tab on github and find a solution
6 - Implement the solution, recompile and send 2 apk files to Console
7 - Did not work...
8 - Find out maybe the console will allow just on closed alpha and beyond
9 - Put apks on closed alpha and fail because the Console wants a new apks with increased version codes...
10 - Recompile and send apks
11 - Console won't allow launching unless the format is using the new App Bundle
12 - Flutter does not support App Bundle with 32 and 64 bits...
13 - See issue about it saying the possible fix is in beta version, just need to update... What could go wrong?

I just wanted to release a damn app

I hate that shit

I downloaded somebody's GitHub code to use for a project. It had a bug that broke functionality, so I fixed it and started running it to gather data. Then it stopped working for a different reason. I rechecked out the code fresh, same (second) issue occurred. It was a second bug, that once I fixed it, everything worked. But I didn't need to fix it the first time! There weren't any commits in the last two months! I blame ghosts.

So, I am feeling low in life. I want to do so many things and not a single one is going as planned. On top of that Bitcoin has taken a plunge and my funds are stuck with a shitty exchange and I cannot withdraw till tomorrow.
Le a github issue appears and I am thinking what went wrong now. I had added a few new features to the app which would have broken the old configurations. So, I ask this guy to re-configure and test.
After about 2 hours I get a reply from the guy saying "Thanx for the great new features and for creating this great open source project!!!"
This made my day. And I am thinking Life's good. Life is so easy and we make it so difficult for us. The first thing I am doing after this review is write this rant. Now back to work.

Couldnt fix a bug that conflicted with an unrelated codebase. A 1 in a million issue on github.

Had a wank.

Bug fixed, pushed, and deployed 30 minutes later.

Github Issue Template:
"Create a report to help us improve - please use detailed titles"

NOOOO!!!!
devRant!!!!!
Who did this to you :(
The Avatar Builder ... you have ...
A BUG
dfox & t-rogus:
1366x768 px
Arch Linux, Firefox

Are my rants supposed to be well documented, too? Or like submitted as if it’s a GitHub issue, where I shall add details such as what’s not working, how do you expect it to work, steps to replicate the bug, screenshots?

Why tf am I even overthinking this?! Lmao

I just wasted 4 hours debugging a wordpress plugin because the API was returning only the first element of a list. I posted it on support forums, downloaded the plugin's source code and tried to manually find the cause, and I was about to post an issue on the plugin's github page.

It turns out that I forgot I had '$[0]' in my insomnia json filter.... I should probably look for a different job.

Currently reading through a long GitHub issue thread. For some reason people started quoting the entire message they are replying to.
The last post has 9 nested messages and the quote section is 1600 pixels tall. Who needs @mentions anyways.

"This is ridiculous, why don't the docs explain this? This is absurd, it seems like thousands of people should be having this issue. Why do maintainers fucking not get it? Why write software if you don't intend for anyone else to use it?"

versus

"Hey, could you explain X to me? I'm having trouble understanding it."
"Sure, here: ..."
"Thanks - maybe we could add it to the docs, that's the first place I looked."
"Absolutely, good idea."
<closed in a8b7cb8d>

Which one was easier, folks? It's not this difficult. 100% going to help you if you ask - to me, at least, there's no such thing as a stupid question (seriously, I'll answer the most inane questions 100 times over if I need to). However, there's definitely a stupid comment, and unfortunately they seem to be the majority I receive on Github.

When your tech lead revokes everyones merge priviliges on Github because of an issue with "code disappearing from the repo" which he originally suggested was a bug in Github and we should call them for help.

To peoples asking on StackOverflow or making an issue on Github:

Please, include enough code to reproduce your issue.
But don't put your entire project either

It should be as easy as possible to run and read your code.
Otherwise, peoples trying to help will get lost and give up

!rant ?

So I had 2 Stack Overflow questions open about Rails / Webpack data communication, plus one issue open on Webpacker's github for 3 days, desperatly looking for an answer or an idea. No answers.

Today I talked a bit with my flatmate about my problem, dude gives me a perfect, easy to implant solution, and life seems to be bright again. Thank you Alex 😥.

Just had my first issue raised on my GitHub project!

Not sure if that's a good or a bad thing...

Created a github open source project for voice recognition for react native Android.

Needed help developing some features and did my research with links to some articles.

Then some guy that showed interest in the specific issue just copied my repo and launched his own npm package with the new features.

Just threw my code in the garbage and just felt so irritated. I did all the research and shared the research links and he just duped me and left me to rot. No credit given.

Fuck that guy. This is not open source.

Rant over

To be honest I forgot completely about the ducks and was kind of disappointed to see them, don't understand me wrong, its a great addition to the shop (especially to support devrant more when buying them and I will probably do too) and trogus (wow it's pronounced t-rogus) deserves a lot of respect for going through the very hard process of developing it, getting somebody to do a decent quality result etc. but I was hoping for the new site that got hyped up some time ago or some update to the app that fixes design issues on phones that have 2k resolution and no statusbar and more. ("just open a github issue" - I don't have one right now and it didn't get much attention anyway, since I am in the niche of people with those kind of setups, most people it seems have phones that can even barely run the app lol). The login still pops up each time you visit the site (basically just click it away, but it's rather annoying to have it pop up), it's nowhere near to the original app (although the native app is written in some sort of wrapper anyway?) - especially what comes to options, customizing, deactivating things, posting into categories (newest feature), getting notifications etc

There is some community builds that try to recreate a better desktop experience, but sadly fail to do so (sorry to devrantron and others, but what the fuck were you thinking when you rounded only the top right and left corner?) - since they always have something that is just thrown out to "be there" or design fails (which devrant just lacks and looks good across the board), that makes me rather cautious if that program doesn't send my credentials to some african prince. ("just look at the sourcecode", yes I have better things to do, thanks)

I could just create my own build, having to reverse engineer the whole website and app (granted, most of it are just api calls), but I simply lack the time (so I understand why my mentioned problems aren't getting really any attention or can't be implemented that fast, yet still its somewhat bugging)

I have listened to the Q&A and I know you guys are working full time at for example adobe (amazing that you both have time to be putting it towards devrant), so its not as much of a rant, just wanted to get out my disappointment about the event I felt personally. Still nice to have seen you and talk with the community a bit (although the time I feel was picked more towards your US audience rather than EU?).

So my friend works in this big MNC company with good pay. He has had good education and certifications. He runs into a simple issue with someone's github project he forked and calls me for me help to debug the issue. Just helped him figure out the reason for issue over the phone.

And here I am technically "jobless" and loser in my relatives eyes because I'm pursuing self employment with no cool certifications to brag about.

Not sure if I should feel stupid for the choices I made in my life.

A close friend of mine and i talked a while back and it went a little like this.

friend - "You like programming right"?
me - "Yeah"
friend - "I got a great idea"

She never really told me what the whole idea is. She said its easier to explain face to face but i can guess it's dev related.

But here's the issue. I have a tendence to just suddenly loose all motivation for a project (look at my github) and i'm afraid that i'll loose motivation for the thing she wants to do with me and i'll disappoint her.

Do i help her with her idea or not?

Keep in mind that i'm not a actual dev. Its just kinda my hobby. I can do it for free. Thats not the problem.

#rant People referring to Zenhub when they mean Github. "I created an issue in Zenhub".

"DO NOT USE ISSUES FOR GENERAL SUPPORT.
Issues are for request only. You can use the following:

- Stack Overflow (using the "traefik" tag) (where no question excepted the simplest are ever answered)
- the Traefik community Slack channel (where no one is online)

...

So, what should I put as a title for my "issue"...

Recently GitHub announced it is gonna preserve the world's open source code for next 1000 years. Great initiative! But someone has to take initiative to store StackOverflow data too! What if after 500 years someone tries to use Tensorflow and gets dimensionality issues? And imagine there won't be any StackOverflow to solve the issue.

Remember : Wherever there is a code, there is a bug.

-- 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 fucking hate environnement configuration so much that I prefer to debug 8 hours straight rather than lose my time and shit for 2 hours on idiotic configuration problems and jump from page to page like a dumbass

"Hey you want that module, download it here !"
"Oopsie, starting from X version of the JDK/JRE this is no longer standalone and directly embedded in"
"Can't find it ? Well I just forgot to tell you that starting from Y version this is COMPLETELY removed from what I just told you to search in and now in another standalone package"
"So now you added your package as dependency for you project, your IDE detects everything well but can't run your code ? That's because it doesn't work anyway, use another method found on the dedicated Github issue which makes little sense and that you have to apply everytime, then sacrifice your inexistent newborn to connect to the 9th circle of hell where Java resides so everything will work"

I knew I couldn't get away using fucking Java and JavaFX

Anyone have any idea why release downloads from GitHub is slow af?!

It is not a network issue on my end.

Any ideas?

I've just seen this issue on Github. What's so special would you ask? I've developed Aria2App, I'm feeling so nice.

Yesterday my friend called me programming Jesus for getting her code to work properly

She's started learning python. All I did was fix the indentation issues and explain that whitespace is finicky in python and send her a couple of article links about it. pretty boring of an issue

I'm kinda bored I wish someone had a more substantial issue for me to look at and have to actually learn something new to fix it

Considering finding a project on github to try and contribute to as a side project when I need a brake from my projects. But as a worse-than-mediocre college coder I'm intimidated to even try

How to make enemies of a lot of people very quickly with a github issue SPAM.

Not wanting to do any more work because you've just closed the 69th issue on GitHub

What's worse than a StackOverflow question with no answers? An open GitHub issue, no comments in the last three months, and a sense that you just hit the ultimate bug the vendor will never fix.

That feeling when your github issue you created four years ago that generated hundreds of thumbs up is locked in the end by the maintainer without any intent of fixing it as a solution would be a breaking change.

Never mind the fact that the default was off to begin with.

I get it, it's open source and it's their tool and I should keep my sense of entitlement in check and just be thankful that they provide it.

But damn, you'd think that some sort of feedback would reach them in their ivory tower.

> be me
> change theme in vscode
> syntax highlighter stops working for php
> panic mode
> removed personal settings for php
> removed all settings
> back on default
> ohshitno.xml
> find a github issue, marked as closed
> sleep
> wake up
> start working
> cannot work without syntax highlight
> find another github issue, saying the theme I want doesn't supports syntax highlighting
> fml.xml
> back on default

bitter reflections from a bitter dev on hacktoberfest this year (in the past 2 hours of trying to find issues my IQ has at least halved):

- DefinitelyTyped - used to be my bread and butter to complete hacktoberfest; now, not sure if actual issue, or person just doesn't know how to use typescript (found a multiple such issues that were actually non-issues, the type they were asking for was right there, no pull request needed)

- avoid "issues" on no code / low code tools, these are toxic issues with titles like "I EXPLAIN BUG HERE", then probably not even a bug / more a feature request or clueless clown

- if your entire contributor team has the same character styled profile pic + background, i can't take you seriously; if your identity is so closely tied with what github team you are on... uh, i mean cmon what is this kindergarten? (also love the fact that an anon managed to get themselves mixed in hahahaha they ruined it perfectly!)

- most 'hacktoberfest' issue finders themselves are broken or don't load anything

- people claim issues and then never return YAWN

- the hacktoberfest discord: the projects channel is mostly people promoting their garbage repo WHICH HAS 0 OPEN ISSUES IN THE FIRST PLACE AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA and then OTHER people promoting their own portfolio on hacktoberfest???!! 😂😂😂😂 yeah bro i'm gonna help you with your own portfolio site GTFO

from what i've seen, i think i can start working approximately 5 minutes a day and be more successful than these absolute 🎪🤡🤹‍♂️ devs

sure, there is being a beginner, and there is being a clown salesmen trying to get people to do work for you... i mean wtf is going on

i WANT to help and contribute, but this year its really a struggle to find anything worthwhile to contribute to!

somehow the spark is gone... this might be my last Hacktoberfest... let me just return to my wisky and be in peace

hey guess what

commenting "I have this problem too!" does absolutely nothing for a github thread. ABSOLUTELY nothing.

you are bad and you should feel bad

goodbye

What should i do more to get people to read posts properly?????

Question: I completed a feature on separate branch. Since I'm not allowed to merge things on the master branch (only pm is allowed to) I open a pull request.

However, PM has decided that he will only accept PRs which can be automatically rebased & merged.

So now i opened my PR and PM says that GitHub complains that the branches cannot be automatically merged.

So I rebase the branch - push and tell him to try again. But the same issue - GitHub won't merge the PR. So I try again - rebase the feature branch onto master which runs me through the same rebase steps as on the last try. I successfully complete this one too and push. But still - GitHub won't swallow the PR.

Anybody an idea what could've went wrong here?

Dear @dfox and @trogus

I'm writing this here because reporting such issue to GitHub doesn't seem to do it's justice.

It's been happening for like HALF A YEAR.

AND IT'S YET TO BE PATCHED.

WHY. WHEN I CLICK THE BACK BUTTON ON MY PIXEL 2 XL (ANDROID 9). ALWAYS CLOSES THE APP?!?!?

Yes, this is a rant about DevRant, I have no complaints other than this exact one.

It's been happening for way way WAY too long, and never been patched.

Please don't reply to me "why don't you report it on GitHub?" ITS BEEN REPORTED OK?!

I've always loved DevRant since I first joined, but this issue is preventing me from browsing it every time. It's jus irritating.

Please, @dfox and @trogus, try and for once take the time to try and fix it.

Thank you.

Can we normalize NOT using giant acronyms in GitHub issue threads? Nobody understands what you are saying.

The same goes for you, HackerNews users, we can't psychically jump into your ASCII LOL DDD ABC XYZ brain and automatically know what you mean.

Today I spent 9 hours trying to resolve an issue with .net core integration testing a project with soap services created using a third party soap library since .net core doesn't support soap anymore. And WCF is before my time.

The tests run in-process so that we can override services like the database, file storage, basically io settings but not code.

This morning I write the first test by creating a connected service reference to generate a service client. That way I don't need to worry about generating soap messages and keeping them in sync with the code.

I sent my first request and... Can't find endpoint.

3 hours later I learn via fiddler that a real request is being made. It's not using the virtual in-process server and http client, it's sending an actual network request that fiddler picks up, and of course that needs a real server accepting requests... Which I don't have.

So I start on MSDN. Please God help me. Nope. Nothing. Makes sense since soap is dead on .net core.

Now what? Nothing on the internet because above. Nothing in the third party soap library. Nothing. At this point I question of I have hit my wall as a developer.

Another 4 hours later I have reverse engineered the Microsoft code on GitHub and figured out that I am fucked. It's so hard to understand.

2 more hours later I have figured out a solution. It's pure filth..I hide it away in another tooling project and move all the filth to internal classes :D the equivalent of tidying your room as a kid by shoving it all under the bed. But fuck it.

My soap tests now use the correct http client with the virtual server. I am a magician.

Oh god i have been fighting with exoplayer library and ima sdk for past month and yet i haven't been able to figure out how to play multiple VAST tags without using a vmap.. if anyone knows this( or find this relevent and want more info regarding this) please, let's chat.

I am sometimes so irritated with open source. We are grateful that you made a great video player , but please for the love of god , document it nicely. No one can skimm through your 800 fucking classes, especially when a quarter of them are core c++ classes that an android dev never even touches.

Plus no replies on issues! My god, you know after SO, the second tab that's almost always open on my PC is that of some github library or issue. And am sure that must be the case of most of the devs. Then why can't you fucking reply?????

You see, this is typical google.. i am beleive they see everything and ignore it until the right moment comes... Android dev summit is coming, and they won't make any replies now, but would make big changes on the day of their on stage presentations like a boss, recieving lots of applauses, like " yay, they fixed it!! Yess more documentation " bull fucking shit.
My boss knows this and he is on my ass to find solutions before google releases solutions coz he wanna stay ahead of the competition
Thanks for fucking me, open source

I just love it when the debugger integration into the IDE breaks for no good reason.

I also love that the github issue about it was closed for inactivity. Because problems magically disappear if no one screams "same issue here" for long enough.
Fuck you too

Wanting to write some useful open source Java for my github portfolio. Biggest issue is that somebody has already done it for anything that comes to mind :(

I just got an some ESP32 so I started playing with idf by espressif that it's released under apache 2.0.
So i thought "it's open source"
I spent 10 minutes searching for low level WiFi and BLE APIs on github.

Then I found an old issue
where an espressif dev says:

"The low level Bluetooth & WiFi implementations are proprietary"

FUCK!

they distribute Binary files in another repo also under apache 2.0.

any suggestion?
-- (obviuosly) except reverse engineering.

So I coded minesweeper and because I thought it would be fun, I also coded a multiplayer mode. Then I uploaded the code to github. Since this was an Assignment, I wanted to download the zipped code and send it to my teacher. Imagine my surprise, when Chrome told me: Failed - Virus detected. Same with Firefox and Edge. Wow. I didn't think my code was that bad🙃. I then tried to download the release executables I uploaded, expecting for them to fail the test too, but nope, the . exe and the . jar work fine. Google also didn't say much about it. I found a github issue, that talked about a similar problem with the zipped source code, but wasn't much help. What is going on? Anyone have an idea?

> Work with Spring Boot
> Find a bug in an official Spring Boot Plugin
> Open a GitHub issue offering to fix it yourself
> Wait a month
> "status: waiting for triage"

I love Pivotal Labs professionalism

Can somebody create an issue on github please, I am dying 😭

If GitHub now supports "unlimited" "free" "private" repos, how will they generate revenue? Does this mean advertising will be an issue with GitHub?

me:task assigned is a small fix.Gonna finish Early sit back relax this sprint.
mail(next day):we've moved to microservices.setup as easy as gulp landscape:start
me:cool!shinny new stuff!seems easy!!
project:npm failed..please check module xxx..
me:fine.....
after long mail chain
project:npm failed unknown file not found
me:fine.....
after hours of googling and little github issue browsing
project:server running @ portxxx
me:yay finally happy life!!makes chnages, sent for review.
reviewer:code needs refactoring!!
me:make all changes..waits for faceless reviewer from another timezone!
reviewer:thumbs up.
me:i will make it in time!!!yes!!
jenkins:buid:failure
me:no still i wont give up...
debug finds out new bugs caused by unrelated code...make new PR the end is near,one day more will definitely merge!!!
mail:jenkins down for maintenance!
me:nooooo....waits till last minute gets thumbs up for merge, finally merged in the last second!!

all for 12 lines of code change.
:/
sad life

*never* come into a GitHub repository to hijack all the issues with microscopically different questions that are largely off topic from the original issue.
but if you do, and you manage to go as far as to tell the developers that they are practically lying to your face because after all "you think the same code can easily do that other thing", then go fuck yourself in the arse with the biggest pole you can find and walk straight into hell.

it's probably a better option than my stone cold wrath anyway.

Maybe some of you guys can help me out with this.

I'm having trouble using GitHub for Unity with a repository that I have associated with an organisation.
In GitKraken I have to authorise the app for it to be usable with the repository, but I can't seem to find any simple way to do this with GitHub for Unity.

Anyone else here who's had the same issue, and knows a fix?

>> Herborist fails
>> Fixes QT errors
>> Still fails. Relink issues of libudev ; for weird reasons, it's asking to be linked to librt ??? And it's for a clock-gettime.
>> stack overflow: all about cuda and opencv, which can't be my issue.
>> Some asshat on GitHub comment section: mind your language when you're talking to maintainers.

>> Me: You mothertucking trucker! 😐😐😐

🖕🖕🖕

I hope there's a special kind of hell for project leaders / execs that make the decision to take down the documentation for older versions of a software.

I know we should have upgraded a long time ago, but come on. I have no clue what's going on now, and not much to go on either! All the documentation links in the configurations just redirect to the project's github repo, and I sure as hell am not going to read the whole source code just to find the possible logic behind the issue!

Ugh... Days like this frustrate me so much...

At home, I use Cursor, which is way better than GitHub Copilot, but at work I can't choose. One thing I particularly hate about GitHub Copilot is the way the chat panel appears in the left sidebar of VS Code, on top of the file explorer. That, and their useless, arrogant, and ignorant support (or whatever it should be called) .

I filed a ticket about this issue already in July. Their support claimed that one can already move the chat window to the right. But it doesn't work the way they suggested. In August, they asked me to provide a screen recording. So I went through the hassle of making a screen recording just to prove that dragging the chat window does ineed *not* work. I did my part so I was expecting them to do theirs. What do you think happened next? Nothing! Then, more nothing! And then, they just inadvertedly closed the ticket without a resolution or explanation.

Github, that's a pretty shitty way to treat your customers!

GitHub is down. How about we put this as an issue?

Maybe some desperate genius doing the hacktoberfest challenge would save the sinking world of open source.

Is there any alternatives to Atlassian's Confluence and Jira?

We used to use GitHub projects and wiki, but "the business" wanted a more formalised process and access controls on kanban boards and backlogs.

We started using Jira and Confluence last month, but Jira have been incredibly slow with a horrible interface also Everytime I create a new issue it feels like I'm wasting a lot of time compared to the time needed to setup an issue on GH and add it to a project board, plus the entire team is used to using markdown which doesn't work great on Jira.

I've looked for some alternative but I wonder what you are using out there!

Does anyone else find GitHub actions supremely fucking annoying? Everytime I've used it, I've been like "holy shit it would be amazing if I could do this intuitive action, only issue is it doesn't exist".

[ currently smashing my head against a wall for being too lazy to answer a Github response about a difficulty I had, and while I was writing my answer 3 days after, they closed my issue... I'M A MOROOOOOOON ]

My answer to their survey -->

What, if anything, do you most _dislike_ about Firebase In-App Messaging?

Come on, have you sit a normal dev, completely new to this push notification thing and ask him to make run a simple app like the flutter firebase_messaging plugin example? For sure you did not oh dear brain dead moron that found his college degree in a Linux magazine 'Ruby special edition'.

Every-f**kin thing about that Firebase is loose end. I read all Medium articles, your utterly soporific documentation that never ends, I am actually running the flutter plugin example firebase_messaging. Nothing works or is referenced correctly: nothing. You really go blind eyes in life... you guys; right? Oh, there is a flimsy workaround in the 100th post under the Github issue number 10 thousand... lets close the crash report. If I did not change 50 meaningless lines in gradle-what-not files to make your brick-of-puke to work, I did not changed a single one.

I dream of you, looking at all those nonsense config files, with cross side eyes and some small but constant sweat, sweat that stinks piss btw, leaving your eyes because you see the end, the absolute total fuckup coming. The day where all that thick stinky shit will become beyond salvation; blurred by infinite uncontrolled and skewed complexity; your creation, your pathetic brain exposed for us all.

For sure I am not the first one to complain... your whole thing, from the first to last quark that constitute it, is irrelevant; a never ending pile of non sense. Someone with all the world contained sabotage determination would not have done lower. Thank you for making me loose hours down deep your shit show. So appreciated.

The setup is: servers, your crap-as-a-service and some mobile devices. For Christ sake, sending 100 bytes as a little [ beep beep + 'hello kitty' ] is not fucking rocket science. Yet you fuckin push it to be a grinding task ... for eternity!!!

You know what, you should invent and require another, new, useless key-value called 'Registration API Key Plugin ID Service' that we have to generate and sync on two machines, everyday, using something obscure shit like a 'Gradle terminal'. Maybe also you could deprecate another key, rename another one to make things worst and I propose to choose a new hash function that we have to compile ourselves. A good candidate would be a C buggy source code from some random Github hacker... who has injected some platform dependent SIMD code (he works on PowerPC and have not test on x64); you know, the guy you admire because he is so much more lowlife that you and has all the Pokemon on his desk. Well that guy just finished a really really rapid hash function... over GPU in a server less fashion... we have an API for it. Every new user will gain 3ms for every new key. WOW, Imagine the gain over millions of users!!! Push that in the official pipe fucktard!.. What are you waiting for? Wait, no, change the whole service name and infrastructure. Move everything to CLSG (cloud lambda service ... by Google); that is it, brilliant!

And Oh, yeah, to secure the whole void, bury the doc for the new hash under 3000 words, lost between v2, v1 and some other deprecated doc that also have 3000 and are still first result on Google. Finally I think about it, let go the doc, fuck it... a tutorial, for 'weak ass' right.
One last thing, rewrite all your tech in the latest new in house language, split everything in 'femto services' => ( one assembly operation by OS process ) and finally cramp all those in containers... Agile, for sure it has to be Agile. Users will really appreciate the improvements of your mandatory service.

I was always into computers, ever since I was a kid. Played a lot of videogames on Windows 98 and XP, and a lot of my earliest drawings were level ideas for those games. My first encounters with code were with game creation software like GameMaker, but I barely touched the code proper outside of editing a few variables from other people's code. After that I basically forgot all about it and spent most of my teen years being a shutin.

Skip ahead to my last year of high school without much idea on what to do. I was good at math when I wasn't being a lazy shit, so between that and what my parents expected of me, I was prepared to go to university for civil engineering. However, two things changed that decision, the first being a great IT professor, when me and a friend were so far ahead, he started assigning us some harder work, and suggested we study computer science at university. The second was a super jank and obscure open-source early 2000's game that somehow still has a thriving community and is actively being developed. I stumbled upon it by chance, and after playing for a while, I submitted a balance change on the GitHub repo. Even though it was just a single variable change, that time I got it. That time I saw how powerful programming could be and what could be done with it. I submitted PR after PR of new features, changes and bugfixes, by the time I left there I had a somewhat solid grasp of the fundamentals of programming, and decided to enrol in the computer science degree.

Enrolling was possibly the best decision I ever made (not america; debt isn't an issue), as well as giving me actual social skills, every course I took just clicked. The knowledge I already somewhat intuitively had a vague grasp on from videogames, general computer use and collaborating with russian coders who produced the jankiest shit that was still somehow functional was expanded upon and consolidated with a high-quality formal education. Four years later and I'm fresh out of uni, it was a long road between when the seed was first planted in my mind and now, but I've finally found out what I want to do with my life.

won't know for sure until i find a job though ffs

(Response from a Github new issue: )

"Yeah so you declared this element here while it should have been done there. Also, you can simplify the CSS part by just doing the following: <code>

...Then how about updating your goddamn documentation from which I copied the code you're correcting, heh?

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)

I was casually browsing some issues for a project on github, and I certainly across an issue where someone wanted support for for URI handling (there's a good reason for his request).

I was bored, and I just wrote a script to do exactly that. I'm gonna polish it on Sunday, and then upload it, (plus add a PR).

I look at the "Discover Repositories" sidebar every time I log into github. I've found some really cool stuff that way.

But I'm really confused as to why I keep getting typescript-related repositories there.

I've never created a ts repository
I've never made a pull request that had ts in it.
I've never created an issue in any ts repositories.
I've never even written a single line of ts.
The only reason I can think of is that I was browsing the official typescript language wiki for a few minutes...
A COUPLE WEEKS AGO
Yet sometimes, all 3 repos in the side bar have typescript in the title.

TL;DR: github, please stop pushing typescript on me.

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.

devRant, Ineed your advice / help. This following year I'm going to study in the afternoon again. Since this year I don't have to do an intership, I wanted to start working in the morning. There are some problems though:

I never had a job
I'm still 17 so, even if I can legally work, companies don't like to hire underage people
I'm a punk, so even if I'm a really passionate person and I try to give my best always, I've already had been rejected because how I look (literally)

So, I wanted to know how can I build a professional looking CV and how to show to the requiter my GitHub (and now gitea) accounts, if I should clean my repositories, etc...

I'm basically searching advice on how to get my first job. Skills aren't the issue since I know how to code, manage networks, server infrastructures...

Thanks :D

I wonder how many github issues have been closed by asking the author to implement the feature they've requested for. In the past, I was confident my issue will be resolved by opening a new one when there's no answer in earlier questions. I can't tell whether the nature of my questions advanced or whether it's a new trend. But I've opened maybe 4/5 issues in recent memory, and each time, the collaborators suggest the feature is one I should contribute to their project by implementing. Isn't this their job as maintainers? I'm already working on something that barely gives me breathing space. I encountered a challenge using your library, and your idea of helping is that I dissent from my own trajectory, acquaint with your project /how to implement what I want, wait for it to get merged etc, before continue what I originally intended. Do they think that's worth it?

Is it just me or is this a common occurrence, lately?

Ant.design repo and website just got deleted. It‘s still on npm and there is a mirror on a chinese github fake but this is serious.
I have the weird feeling that this is a political issue.
I will not use or support platforms that are under control of the chinese government (gitee).
The only right thing to do now seems to ditch Ant.d (at least in future projects). Maybe I shouldn‘t trust or use chinese software at all.

Jira does my nut in... recommend me something else that caters for stories/tasks for larger requirements but also works well for general issues like how GitHub just has a single issue list to work through

tfw when a library's test are passing but when you implement it, the same library's (dependency) test are failing.

*Raises an issue on GitHub*

MY 4 COMMITS ARE FAILING SINCE LAST 4 HOURS

today my friend wanted to publish his swift 3 library in cocoapods, set up proper github repository, made a releass/tag then tried to upload cocoa pods. first was success but somehow it turned out to be empty then we changed some settings in cocoapods (moved paths etc) then it started to give errors and such. strangely every fkin time different kind of error.
first realized he is using xcode 7 build tools which lacks support of swift3, then switchex to xcode8-beta tools but again that shit wasnt working. so i noticed that their app switching repo origin to their specs origin.
removed cocoapods from sys entirely, xcode7 as same as cocoapods and installed git cmd tools from homebrew to make it updated. started from scratch same shit also happened.

so i give up and fired chrome to look up issue, it turns out it was problem with xcode-beta and cocoapods entirely, even somebody just 30mins before us also commented on issue with exact same output problems
5hrs for shitty bugs fml...

mfw someone makes completely irrelevant OS-bashing comments in an issue that's barely related to OSs... someone tells him to fuck off... and then he posts a FUCKING PHARELL WILLIAMS VIDEO! ON GITHUB!

i'll go straight back to bed, bye.

When project have errors related to libaraies that I don't fully understand what it does, what is the good habit for more efficient troubleshooting?

Should I read their GitHub documentation and understand the problem on my own first or simply find answer at SO?
And when should I just give up and post an issue?

How do other developers handle local websites that are large in size? Currently the code and site need to be setup for each client for several developers. We use github and bitbucket repos for the code.

The biggest issue is downloading the site files and setting it up locally for each developer. We used Docker for some projects but ran into permission issues and storage space became an issue.

Arch. Arch. Installer uhm Arch.

in an event and checking Github issues. This is what i commented;

"... Otherwise I'll solve your problem tomorrow. Today I'm in an issue.." :facepalm:

How to set the up a stagging environment for a github branch in heroku.
Lets say i have a master branch and a dev branch. All the changes and updates first pushed to dev branch and after successful review and test in goes to master branch.
But the issue is as i'm following the gitflow of keeping the master branch always deployable.since my heroku app is linked to the master branch, when i try to test the dev branch in production environment of heroku,sometimes it breaks for some error.and at that time the sites goes down untill i redeploy the master branch as it's the stable version .So how do i test a branch in heroku production environment while also keeping the the site active with master branch. it that makes any sense 🤡 plz help

So, I have a little issue with a program on Github.
- little ttest script in PHP PDO: works
- MySQL-CLI: works
- the program itself: doesn't work

In all 3 cases, the credentials are the same (checked a thousand times)
maintainer be like: "this issue is most likely caused by invalid credentials or the user that doesn't have the rights"

Not the case since the other 2 test cases did succeed --'

What's the big issue with MS acquiring GitHub?

Like, really? What's the big deal with it?

I don't see any.