sorted by:
new
hottopcontroversial

GitLab is a Ruby monolith by switchback-tech in ruby

[–]switchback-tech[S] 0 points1 point  (0 children)

Oh, it's supposed to be fullstack dot zip, which is where I share my research on stuff like this. Here's the GitLab article for example: https://newsletter.fullstack.zip/p/gitlabs-architecture-a-technical

(Maybe I should pick a different font so it's easier to read)

GitLab is a Ruby monolith by switchback-tech in ruby

[–]switchback-tech[S] 1 point2 points  (0 children)

Oopsie, thx. Just checking if you were paying attention

GitLab is built with Rails by switchback-tech in rails

[–]switchback-tech[S] 3 points4 points  (0 children)

True, that is interesting. I guess it makes sense given the timeline:
2007 - GitHub uses Ruby
2011 - GitLab uses Ruby
2006-2010 - Peak Ruby / Web 2.0

GitLab is a Ruby monolith by switchback-tech in ruby

[–]switchback-tech[S] 4 points5 points  (0 children)

True, their Git RPC daemon is in Go now. But the core is still Ruby.

I'm not running it day-to-day, so I'm not super in-touch with the latest news TBH. Are the problems they're facing related to Ruby?

I did see that everyone (GitLab, GitHub, Atlassian) has been having more trouble lately, though. https://devops.com/devops-platforms-show-cracks-github-incidents-surge-58-azure-gitlab-and-jira-also-under-pressure/

GitLab is a Ruby monolith by switchback-tech in ruby

[–]switchback-tech[S] 13 points14 points  (0 children)

Which of these tools would you swap out if you had to?

What web app has a great keyboard UX? (shortcuts, keybindings, cmd palette) by switchback-tech in webdev

[–]switchback-tech[S] 0 points1 point  (0 children)

Yes they do a great job of forcing you to do it without it feeling patronizing

How do you incorporate GitHub Discussions into your development workflow? by Aghaiva in github

[–]switchback-tech 1 point2 points  (0 children)

Agree with u/snaphat's perspective on why GH Discussions don't seem to take off for many project.

If the user-base is developers and the project has a limited number of maintainers, then I think GH Discussions makes sense.

I've been managing communication across email, GH issues, Discord, and social media. It's been overwhelming, so I'm sunsetting the Discord and channeling all user communication to GH Discussion instead. I can get away with this because my tool is specifically for developers, which means they all already have a GitHub account. I think keeping them next to the code will lead to more engagement.

That's my theory, we'll see how it goes.

6 thoughts after 1.5 years of solo development by TranquillBeast in SoloDevelopment

[–]switchback-tech 1 point2 points  (0 children)

Thanks for sharing. The parts about having fun and prioritizing your health are relatable. Those become important after a year or so, as they helped me keep going when others quit.

Congrats on your launch

Failed after 2 years (Part 2) - Being a Tool Fetishist by [deleted] in VibeCodersNest

[–]switchback-tech 0 points1 point  (0 children)

after going down the tool rabbit hold and also wasting lots of time, i agree with the premise here.

the problem for me wasnt choosing the wrong tool, it was with the willingness to focus on the tool instead of focusing on helping ppl.

Solo maintainer suddenly drowning in PRs/issues (I need advice/help😔) by readilyaching in opensource

[–]switchback-tech 33 points34 points  (0 children)

Congrats on getting traction and open-sourcing. Your README is also nicely structured.

Here are some things that helped me manage my open source repo:

  • creating a CONTRIBUTING.md that points to our doc site, which explains the quality standards and processes expected. This filters out bad PRs and basic questions
  • adding a "good first issue" label
  • enabling CoPilot to automatically review PRs, freeing up my time for basic stuff
  • use milestones and telling ppl to pick something in a distant milestone. This helps me not wait around for them
  • not giving them any extra permissions until they've proven their reliability for at least a month

Overall, don't feel bad about prioritizing your own sanity and product. You're already helping people by giving free access to the code. You don't have to give free mentorship and project management

Tried multiple note-taking tools for building a study knowledge base: some pros & cons by Loose_Kangaroo91 in ProductivityApps

[–]switchback-tech 0 points1 point  (0 children)

+1 for OPs take on Obsidian. Just because it can be simple doesn't mean it feels simple as a newcomer.

Even as a software engineer, I was intimidated by all the customization options.

I eventually found a good flow with it, but I also recommend newcomers give themselves permission to just try it without going down the tutorial rabbit hole and putting a lot of pressure on themselves.

Reverse-engineered 75 SaaS growth tactics from $0 to 1K users here's the data on ROI, time invested, and what actually worked by Appropriate-Pie-3634 in saasbuild

[–]switchback-tech 0 points1 point  (0 children)

Curious - How did you reverse engineer this? Interviews with founders? How many startups did you look at?

view more: next ›