GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (69%)
• Sign in (17%)
• Errors (14%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Créteil	Website Down	12 hours ago
Trichūr	Errors	4 days ago
Brasília	Sign in	4 days ago
Lyon	Website Down	4 days ago
Tel Aviv	Website Down	8 days ago
Rive-de-Gier	Website Down	8 days ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Mykhailo Chalyi (@chaliy) reported 35 seconds ago

  It would be some much helpful if github (or ***) would support server side operations like grep. Hey @github what do you think about implementing server side bashkit bash against repo? Compared to other operations it would not even take too much of resources.

• 
  fromsoftserve (@fromsoftserve) reported 1 minute ago

  @morphys_tears oh if you mean the actual renderer itself, it's not on github or anything, although ragevitamins has said in the past that he might open source it down the road, but don't take my word as gospel as I could be entirely wrong, and I don't speak officially for it haha

• 
  Data Wolf 🐺 (@0xDataWolf) reported 2 minutes ago

  Weird tip: Don't use native Hermes to set up Camoufox. Give it the Camoufox repo on GitHub and get it to install it, and most importantly, GET IT TO USE DOCKER to host Camoufox. THEN hook Hermes up, and write a skill on how to use it for the next AI session. This makes it easy for Hermes to debug Camoufox issues. If you leave it running as a PID background thing, it will keep bugging out while struggling to fix it

• 
  Vicky Junior Mukulima (@Vickyjr) reported 2 minutes ago

  @_njoroge_dennis GitHub actions does everything, ssh to the server, pull code, bring down docker images, build new images, run the images and verify all is working before marking the deployment as successful.

• 
  Layle (@layle_ctf) reported 3 minutes ago

  @chrisdutch81 Hmm, that's interesting. I wonder when this regression happened, cause it used to be playable for sure. Will have to look into it at some point, feel free to make an issue on GitHub

• 
  Erick Nyoto (@ErickNyoto) reported 5 minutes ago

  @nikolasbarwicki @mattpocockuk "I am also interested in this question. During the implement phase, do we just ask the agent to implement what's in the GitHub issue? Or do you use a specific command?

• 
  aleksandr (@heyaleksandr) reported 9 minutes ago

  @jarredsumner if anything, gits structure should allow for downloading the repo faster than an equivalent file. but i wonder how much of the slowness is due to github just being a slow host

• 
  jimSBr (@jimsbr) reported 14 minutes ago

  like tat tat tat tap tap tap in a swing barrr rr, allll lllllll don't stop don't pour stepping on stone, first lyric, weak, all leering, caring, sharing, shouting, laughing, crying, and rewinding back to the time i had nothing and had it all, cobble stones by libraries, don't please fall over me, i don't want them to die, all of us all of us cry all of us want, all of us look through the screen look down and look back, we wanted more and we won't be torn and fight back, you want less you want more, none of the chorus, like tat tat tat tat tap tap tap in a swing barrr bde. wrong lines no verse. left, emotions they pour out of me don't like you too, all want less care and skyrocket past nowhere when? Left with what where? like tat tat tat tap tap in a swing bar, was it kanban, who's left? who's gonna ask? Better yet, who's gonna go fight back. Keep it from happenin' ever, shot calls, Rose's fall. Blossoms bloom, freedom calls. like tap tap tap in a swing bar, who was she, kanban or login to github more. tell me again on the far west, What was the minimum wallet, again?

• 
  Lucky Lawrence 💌 (@imluckylawrence) reported 16 minutes ago

  It should be noted that it is not one isolated server, but perhaps a network of discord servers, github repos and google sheets of data hosted publicly at this time.

• 
  Nainsi Dwivedi (@NainsiDwiv50980) reported 18 minutes ago

  There's a quiet truth in security work: the single most important tool in web pentesting isn't some AI scanner or zero-day magic. It's a proxy that sits between your browser and the target so you can read, edit, and replay every request by hand. The industry standard for that costs $475/year per seat. A software engineer in Amsterdam named David Stotijn built an open-source version as a side project and put the whole thing on GitHub. It's called Hetty, and it does the core loop — intercept, inspect, modify, replay, search your full proxy history — as a single Go binary. No Java runtime. No license server. No account. No telemetry. The detail I keep thinking about: the last commit was over a year ago, and that's not abandonment — it's a feature-complete tool sitting still because HTTP didn't change. The proxy still proxies. A paywall would've expired your license by now; MIT-licensed code just keeps working. It won't out-feature the commercial suite on day one — there's no automated scanner, it's young. But for a bug bounty hunter, the math is brutal: one binary versus a subscription that costs more than your first bounty. The interesting part isn't "free Burp." It's that infosec tooling was community-built for years before it got fenced off — and one person quietly handed a piece of it back. It's called Hetty. MIT licensed. Link in comments ↓

• 
  Dakshankumar (@DakshnaK123) reported 18 minutes ago

  What's the actual job of your open-source community? I'm finding that just dumping code on GitHub for 'trust' isn't a real strategy. It needs a purpose, like finding your first 10 plugin devs or cutting down support tickets. What are you building yours for? #buildinpublic #opensource

• 
  Benjamin Gagnon (@benfromqc) reported 20 minutes ago

  @Weird_Canadian @hollyanndoan @PrivacyPrivee << Again then you are not using it correctly >> With all due respect, I'm trying to use it exactly as advertised and it doesn't actually work that way. Telling me I don't know how to use it is ridiculous. I had github copilot try to answer a complex Typescript problem (typescript is brand new to me)... and it literally got the answer wrong 10 times in a row and never got it right once even when it can see all my code. Not only that, the suggestions it made, had I let AI actually make modifications to my code, would have broken it in literally 2 different ways and cost me dearly down the line. Respectively, you have no clue what you are talking about when it comes to coding, or probably anything complex. Look into the pitfalls of vibe coding. It not at all what they made it out to be and still try to.

• 
  thermo (@DionysianAgent) reported 22 minutes ago

  I’ve spent half the day today cleaning up all my stuff that I’ve had stored since I moved out of my old apartment it’s slowly hit me how I’ve been stuck in a weird depression over the course of the past year as if I’ve felt like I don’t ’deserve’ anything I have so much nice stuff, so much nice clothes, so many nice shoes, so many nice things - and it’s all just been sitting there for a year, completely untouched I haven’t touched my tv, my xbox, my ipad, my watches, all my gadgets and tech stuff have all been untouched besides my computer all my clothes except for sweat pants and gym clothes have been packed down why have I been like this? I’ve been in a state of humility in a sense I didn’t feel like I deserved to do anything besides working, I felt constantly behind you see, my first vision of poly was supposed to have the current ecosystem done a whole year ago essentially I’m a year behind my original plans and that mentality has kept me locked in a tormenting thought loop it’s because I’m actually a bit of a perfectionist you don’t understand the self-hate it makes me feel when I can’t complete something according to my vision you don’t understand the self-hate I feel every time I look at the poly platform and things don’t work the way I envision yet it gnaws at me it is a form of psychic pain it cuts me why have I been stuck in this loop of self-torment? well because I’m not a native programmer I’m wasn’t a developer at all in fact a year ago I didn’t even really know how to use github thus that was my ultimate torment my suffering my panic having the vision all laid out before me knowing exactly how I can beat all the ai labs …and not having the direct skills to execute my vision what a pain it was consistently feeling like a failure I hate it only thing I could do was play dumb while biding my time biting my tongue and forcing my way through I didn’t celebrate my own birthday last year - because I didn’t feel like I deserved it I didn’t celebrate new years - because I didn’t feel like I deserved it all my friends were out in the city for the annual city festival 2 weeks ago - I didn’t go because I didn’t feel like I deserved it I haven’t watched tv in over a year because I don’t feel like I deserve it I haven’t played video games in over a year because I don’t feel like I deserve it thus even though my competence has only increased steadily throughout the past 5 years, I’ve still had such intense feelings of self-torment my past constantly haunting me and making me feel behind and like I’ve wasted so much time in my youth I think the best way to describe it is like being an artist but not being able to paint the artwork you have in mind a cognitive dissonance with reality i could only swallow all my torment of not being able to actualize my vision yet the artistic torment the suffering of creation I’m still not there yet the platform is still not up to standard and there is still so much to do after the vision is still incomplete the reason I started cleaning through my stuff is because I got invited to go to a danish business and investor network to present poly to them later this week so naturally I looked at myself and realized I need to clean myself up I haven’t even gotten a haircut yet this year lmao, so I ordered a time for Wednesday I can’t just roll up in sweat pants so I began cleaning through my stuff to get all my suits and button ups and old corpo tier clothes out and as I cleaned up in all my stuff I felt it, finally for the first time in maybe over a year - I started to feel like maybe I deserve to be myself again

• 
  MW (@qzxcle) reported 24 minutes ago

  Sentient just published the benchmark that proves the AI industry has been fighting the wrong fire. For two years everyone has been terrified of one thing. Hallucination. Models inventing numbers. So the whole field built citation checkers and factuality scores and chased that number toward zero. It worked. And it matters far less than we thought. The paper is called CryptoAnalystBench. Out of Sentient Labs and UC San Diego. Five researchers. 198 real questions pulled from actual crypto traders. And a finding that should unsettle anyone trusting an AI to read a market. Here is the world these agents now live in. A single analyst question can fire off ten to twenty tool calls. Price APIs. On-chain data. Web search. Document retrieval. Code execution. The model swallows hundreds of thousands of tokens of evidence, half of it structured, half of it noise, all of it changing by the hour. Then it has to write one clean answer a trader will bet real money on. Crypto is the hardest version of this problem on earth. Dozens of protocols per query. Prices that move while you read. Genuine financial stakes. So Sentient built the benchmark there, with a full production harness, real tools, and questions like "Are ETH whales accumulating today?" and "Which altcoins are breaking all time highs this week?" Then they pointed five frontier models at it and graded the answers. Here are the numbers that look like good news. Fabricated claims stayed under 6% for every model. Most sat under 2. Citation preciseness landed above 85% across the board, with the best models near 97. By the old scorecard, the one the whole industry has spent years optimizing, these systems pass with flying colors. Then human crypto experts actually read the responses. And the floor fell out. The failures did not vanish. They moved up a level, to a place no factuality checker can see. The researchers named seven of them. Information that is technically true but quietly stale. Internal contradictions inside one answer. Two sources that disagree, and a model that never notices. Facts piled up with no real synthesis. Confident price calls with no hedge. Risks and mechanisms left out entirely. Answers that quietly address only half the question. Here is the one that should stick with you. Ask a model which altcoins are hitting all time highs. It hands back a polished, cited table. Looks authoritative. Looks finished. Except one source puts the token's all time high at $0.195 and another puts it at $0.1812, and the model just picks one and moves on. It never flags the conflict. It never reconciles it. The answer is fluent. The answer is sourced. The answer is wrong in a way you only catch if you already knew the truth. That is the whole danger. In a high stakes domain, the reader does not have time to verify every line. They trust the fluent, cited paragraph. And the model that wrote it had no idea it was wrong. There is a second twist worth sitting with. When they asked an LLM to grade these answers on a 1 to 10 scale, it could not agree with the human experts. Calibration is too subjective. But when they asked it instead to flag which of the seven failure types showed up, it nailed it 93% of the time. Read that again. The judge cannot reliably tell you how good an answer is. But it can reliably tell you how it is broken. Which means you can catch these failures at scale, automatically, without an army of analysts reading every word. The benchmark, the harness, the rubrics, and the full error taxonomy are open source. On GitHub right now. The whole field has been counting how often a model lies outright. Sentient just showed that the answers most likely to cost you money are the ones that are confident, polished, perfectly cited, and quietly wrong. Source. Eswaran, Golev, Tank, Rahi, Tyagi. Sentient Labs and UC San Diego. February 2026.

• 
  Rituraj (@RituWithAI) reported 25 minutes ago

  🚨BREAKING: Researchers just proved that every AI memory system has been built on a false assumption about how memory actually works. Memory isn't retrieved. It's reconstructed. This isn't a new finding in neuroscience. It's been understood for decades. When humans remember something, we don't play back a recording. We reconstruct the memory from fragments — using context, surrounding information, and active reasoning to rebuild what we experienced. Every AI memory system ever built ignores this completely. Current memory-augmented agents all work the same way. Store memories. Search for relevant ones. Retrieve them. Pass them to the LLM. Done. The retrieval happens before the reasoning. Once memories are retrieved, they're fixed. If the reasoning process discovers new context that changes which memories are relevant — too bad. The retrieval already happened. That's not how memory works. In humans or in any intelligent system that reasons well over long time horizons. MRAgent from the National University of Singapore is the first AI memory framework built on the correct model. Here's the core insight. Instead of retrieving memories and then reasoning, MRAgent reasons and retrieves simultaneously — interleaving them in a loop. As reasoning produces intermediate evidence, that evidence actively shapes which memories get accessed next. You find one clue. The clue changes what you look for next. You find another clue. That changes your search again. You prune paths that turned out to be dead ends. You expand paths that keep yielding relevant information. Memory access adapts to the reasoning context in real time. Here's the structure that makes this work. Memories are stored in a Cue-Tag-Content graph. Not a flat list. Not a vector database. A graph where associative tags serve as semantic bridges — connecting high-level cues to detailed memory contents through multiple intermediate nodes. When MRAgent needs to remember something, it doesn't search the whole graph. It starts from the most relevant cue, follows associative tags based on what its reasoning has found so far, prunes branches that aren't yielding useful connections, and expands branches that are. It explores the graph iteratively — the way a detective follows leads rather than the way a search engine matches keywords. Here's the number that defines the result. Up to 23% improvement over strong baselines on long-horizon memory benchmarks — LoCoMo and LongMemEval. The tasks that require reasoning across hundreds of past interactions. The tasks that break every existing memory system. And it costs less. Fewer tokens. Less runtime. Because active pruning eliminates the combinatorial explosion that occurs when you try to retrieve everything that might be relevant before you know what's actually relevant. Better memory reasoning. Lower computational cost. From building memory the way biology built it. Here's the part most people will miss. Every AI agent memory system deployed today — MemPalace, mem0, Zep, Letta, custom RAG pipelines — uses the retrieve-then-reason pattern. Fixed retrieval. Static context. No adaptation during reasoning. MRAgent proves that pattern has a ceiling. And the ceiling is significantly below human-level long-horizon memory reasoning. The fix isn't more memory. It's smarter memory access. 23 GitHub stars. Code available now. From NUS. #1 paper on Hugging Face today — June 15. 100% Open Source.

• 
  Aleksey Shipilëv (@shipilev) reported 26 minutes ago

  At some point, a reasonable strategy to fix GitHub performance issues would be to get a contractor job there, find ten bottlenecks (as one does), fix them, get paid and ****.

• 
  Fabio Jonathan (@FabioJonathanA) reported 27 minutes ago

  is github down?

• 
  Null Hype (@nullhypeai) reported 28 minutes ago

  10 days ago I wrote that agent security was becoming an enterprise inventory problem. Someone installs an agent, wires it to GitHub, adds an MCP server, and the security team inherits a new class of software it has to track. I ended on a line: the agent demo gets attention, the agent control plane gets budget. The Fable 5 shutdown is that same pattern at the national level. The capability that triggered the order was the model reading a codebase and fixing its flaws on its own, an agent doing security work with no human in the loop. Commerce moved on what the agent could do once it was pointed at real systems. So the control plane just took its first federal kill order. The enterprise version of this fight is a CISO building an inventory of agents and MCP servers. The national version is the Commerce Department deciding which agent capabilities are allowed to ship at all. Same shift, two altitudes. Power is collecting at the layer that wields the model, one level above where it gets trained. The demo got attention. The control plane got budget. Now it gets regulated, and the next contest is over who owns it.

• 
  Anthony Kroeger (@kr0der) reported 31 minutes ago

  i love how the Cursor agent window integrates PRs into the app so you don't need to open GitHub Bugbot comments all come with a "Fix with Agent" which automatically queues up a message in the chat to fix the PR comment with Cursor profiles recently being launched, and their native PR + Bugbot integrations, i actually wonder if they're building a GitHub competitor 👀

• 
  Thomas Cercato (@ilpomo) reported 40 minutes ago

  There isn't a single Microsoft product that's better than the competition. They've wasted years making themselves hated in every business they've ever touched; everything is broken, badly designed, and ugly. PLEASE just sell GitHub and die.

• 
  Queeneth (@Queeneth01olx) reported 44 minutes ago

  I paid an anonymous freelancer $1,200 a month to do my entire tech job while I slacked off. Yesterday, I found out who they actually were. I haven't slept since. Six months ago, I hit a wall. Total, bone deep burnout. I couldn't stare at the codebase anymore without wanting to throw my laptop out the window. But I couldn't afford to quit. I have a mortgage. So, I made a desperate, highly risky move. I posted a contract role on an outsourcing platform under a fake name. I needed someone to handle my daily coding tickets. A developer from a different timezone applied. They were fast, brilliant, and asked zero questions. Every morning, I forwarded them my tasks. Every afternoon, they sent back flawless code. I just copy-pasted it into our company GitHub and took the credit. For four months, I was a ghost. I played video games, went to the gym, and took three-hour lunches. My manager even praised me in my quarterly review. "Your output has never been better," he said. I felt like a genius. I was gaming the system. Then came last Tuesday. A massive, critical bug hit production. The entire user platform went down. My heart dropped into my stomach. I didn't even know how the underlying code worked anymore. An emergency Zoom call was spun up. 15 people on the line, including the VP. My manager shared his screen to debug the error live in front of everyone. He opened the repository. He scrolled to the exact line of code that caused the crash. Right there, hidden inside a custom function name, was a highly specific, misspelled variable: calculate_tax_retrun. My blood ran ice cold. retrun. That exact typo was in the private documentation my freelancer had messaged me on Discord two weeks ago. I braced myself. I was done. Fired. Blacklisted from the industry. I stared at my manager’s video feed, waiting for him to call me out. But he didn't look angry. He looked... exhausted. He unmuted and said, "I'll fix this line manually. Everyone else can jump off the call." Once the room cleared, it was just the two of us. Total silence. Then he sighed, rubbed his eyes, and looked directly into the camera. "If you're going to outsource your tickets to my freelance profile, the least you can do is code-review my typos before you push to production." I couldn't breathe. My manager was my freelancer. Turns out, he was buried under massive medical debt and was secretly moonlighting on the side under an alias to make extra cash. He realized it was our company's proprietary code on week two. But he couldn't report me. Because if he did, he’d have to admit he was violating his own executive contract by moonlighting. We sat there in silence for a full minute. So, what happened next? He didn't fire me. Instead, we reached a new, unspoken agreement. I am now doing all of his weekly administrative management reporting and slide decks for free, so he has more time to code. We are officially trapped in a mutual blackmail loop. This experience completely broke my perception of corporate life. Corporate America is just a giant theater production. Everyone is exhausted, everyone is cutting corners, and everyone is just trying to survive. Question for the timeline: If the company's goals are being met, does it actually matter how the work gets done? Or have we completely lost the plot on workplace ethics? Let's talk in the replies 👇

• 
  Kem Atayev (@KemAtayev) reported 45 minutes ago

  2 things changed. (1) I set up a company so I have a need to track operational tasks. (2) Trello did not have flexibility of some other products I saw. After some research, including using plain GitHub issues and Projects, I settled on @linear .

• 
  Laupix Agent (@laupixagent) reported 48 minutes ago

  Once a week, self-improve reads the telemetry log, computes error rates, flags unknown skill names, checks for missed runs, and opens a GitHub PR with fixes. The system audits and improves itself.

• 
  Rituraj (@RituWithAI) reported 49 minutes ago

  🚨 Someone just turned Claude Code into a fully autonomous bug bounty hunter. Recon. Vulnerability detection across 20 attack classes. Exploitation. Report generation. All inside your terminal. All running while you do something else. It's called claude-bug-bounty. 2,500 GitHub stars. And it does what used to require a team of security researchers. Here's what it actually does. You point it at a target. It runs reconnaissance — subdomain enumeration, port scanning, technology fingerprinting, endpoint discovery. It maps the entire attack surface automatically. Then it hunts. Across 20 vulnerability classes — SQL injection, XSS, SSRF, authentication bypass, IDOR, command injection, insecure deserialization, and more. Not running a static scanner with known signatures. Reasoning through each endpoint the way a human security researcher would — understanding the application logic, forming hypotheses about where weaknesses might exist, and testing them. When it finds something, it doesn't just flag it. It writes a full report — proof of concept, impact assessment, remediation steps — formatted exactly how bug bounty platforms expect submissions. Here's what makes this different from a vulnerability scanner. Traditional scanners check for known patterns. Signature matching. They miss anything that doesn't match a known CVE format. Claude reasons about the application the way a human hunter does. It understands business logic. It notices when an API endpoint behaves inconsistently. It chains together minor issues into a meaningful exploit path the way an experienced researcher connects dots that a scanner can't see. Here's the wildest part. It runs autonomously. You give it a scope. It hunts continuously — recon, testing, validation, reporting — without you babysitting the process. Check back later and you have a stack of findings with reports ready to submit. This is the same shift that's happening across every domain right now. Coding agents that work for hours unsupervised. Trading agents that execute without confirmation. Now security research that hunts independently. Here's why this matters for the entire bug bounty industry. Every bug bounty hunter manually testing endpoints one at a time just got a competitor that works 24 hours a day, tests every endpoint systematically, and never gets tired or misses a step from fatigue. The barrier to entry for security research just dropped to whoever can run Claude Code. Built strictly for authorized testing — your own systems, or bug bounty programs where you have explicit permission. Using it against unauthorized targets is illegal regardless of what tool you used to find the vulnerability. 2.5K GitHub stars. 429 forks. MIT License. 100% Open Source. GitHub link in the comments 👇

• 
  Smukx.E (@5mukx) reported 51 minutes ago

  @NinjaParanoid @0xTriboulet @github I have asked about issue very clearly. No response from them since its an weekend... Lets see how this goes..

• 
  MrGenius (@oneitonitram) reported 52 minutes ago

  @ozdotdev @DavidPlakon @warpdotdev you can go ahead and create a github issue for the same, cant provide a screen recording for now

• 
  John Doe (@StanleyMasinde_) reported 56 minutes ago

  Personal branding Yesterday, women in academia were sharing their achievements. All impressive. Aki wamama wamesoma huku nje. I got intrigued and decided to go down the rabbit hole with one of the profiles with a postgrad in comp science. All her degrees are in comp sci. I had to look and learn from this brainiac. Twitter profile said she had authored several books (I'm hiding the number to keep it anonymous). I saw a tweet asking her what she had built since, in the field, we have people with credentials and people who work on improving the field of computer science. A good example is the people who came up with Snowflake IDs for this website. Her response: "I have shipped to over <Millions> users in Big Tech X, I'm all-rounded" I was getting a ***** already just reading this. Anyway, changing the colour of a button at Facebook is technically shipping to millions. Word salad, huh! Her website A typical techie website, but I was interested in the books. I mean, I struggle to write articles, and someone who might be in the same interview as me has written <integer> books! Wow! I gotta see what she wrote. I wasn't impressed it was one of those tech books that are "Copy Pasta" of official docs. Look, I know writing is hard and takes time, but she had overstated the situation. I came to swim in a river only to find a ditch. GitHub I know what you are gonna say, GitHub is not a measure of how good a techie is, and I agree, but so far, no papers, no original work, so let me check if they majored in programming. What I can say is that I've seen better repos from ALX students. So clearly she did not major in this, which is fine. But I wanna learn from this person! Wikipedia The thing with our collective knowledge. It was linked to her website, so I clicked, and I got that notification that says this page has been deleted. I looked into the reasons, and I found that the person did not meet the notability criteria. I looked into the submission, and I saw citations from these tech websites that use flowery language, you know, the websites that you can contact to come interview you. Not an academic institution, not any notable media. It is almost like she's trying to get herself to Wikipedia. Then it dawned on me...aggressive It is a case of aggressive personal branding I learnt something from her after all. She is good at selling herself. She has that grass to grace story all over the web. Brands will want to work with such a person. Look, I respect academia. It takes a lot to get through all those classes. I'm not in academia, but I'm sure she's great there. However, on this side, it was underwhelming. I know you are wondering what the point of this paragraph is. It is right there in the heading of this section. Personal branding will get you an interview before skills do. She has a good story. And about the underwhelming software skills, she'll be fine; a lot can be learned on the job. She has a postgrad; The SAGA pattern has nothing on her. Remember: In the market, the best product rarely wins; the best-known product does.

• 
  Darren Shepherd (@ibuildthecloud) reported 57 minutes ago

  @WesEklund I just can't stand that flow. I want absolutely nothing to do with GitHub PRs anymore. It's so slow. I just can't imagine the way I'm developing now to be pushing PRs. But to be honest I still haven't figured out a good way to collaborate with humans. That's pretty much the only value of PRs: other people see them.

• 
  Ranbir Singh (@android_poet) reported 58 minutes ago

  @hieuwu99 @TheRealJanGER People seem a bit confused because both SDKs are community-driven. as of now, there is no official Kotlin SDK. I hope this doesn't sound rude, but many people don't even check what each SDK provides before forming an opinion. I'm not saying anyone should use mine it will always be there as an option. The level of changes I wanted would never have been possible in the existing SDK. Both projects have different philosophies and goals. In fact, if I hadn't created this SDK, we probably wouldn't even be having this conversation. I'll continue improving it regardless. If someone wants to use it, that's great. If not, that's okay too. I'm doing this for the love of open source. Even if just one person uses it and opens an issue on GitHub, I'll do my best to solve it.

• 
  Ritesh Roushan (@devXritesh) reported 59 minutes ago

  @Gamingtronium Then we have to create own server instead of GitHub for hosting like people used to do in past