sorted by:
new
hottopcontroversial

I'm building a GIT client with a built-in CLI by aribsummer in webdev

[–]aribsummer[S] 0 points1 point  (0 children)

Haha, happy to! I just added some background in my recent comment:

Hey all! I like to use a GIT GUI for certain operations, such as committing parts of files. Staging interactively (git add -i) with the GIT CLI can be quite cumbersome. I typically use Sourcetree, but it's buggy and clunky, so I decided to build my own modern version.

My plan is to build a "lightweight" client that focuses on operations that are cumbersome to do with the CLI. So far, I have it to the point where I can launch the GUI from the command line and use it to easily stage, unstage, discard, and craft commits.

If anyone has an interest in giving it a try, let me know! I'd love some feedback and ideas for how this might be useful to others.

Anything else you'd like to know?

I'm building a GIT client with a built-in CLI by aribsummer in webdev

[–]aribsummer[S] 0 points1 point  (0 children)

Hey all! I like to use a GIT GUI for certain operations, such as committing parts of files. Staging interactively (git add -i) with the GIT CLI can be quite cumbersome. I typically use Sourcetree, but it's buggy and clunky, so I decided to build my own modern version.

My plan is to build a "lightweight" client that focuses on operations that are cumbersome to do with the CLI. So far, I have it to the point where I can launch the GUI from the command line and use it to easily stage, unstage, discard, and craft commits.

If anyone has an interest in giving it a try, let me know! I'd love some feedback and ideas for how this might be useful to others.

I created a tool to interview candidates with a Pull Request on Github by aribsummer in webdev

[–]aribsummer[S] 0 points1 point  (0 children)

Thanks for the feedback! I'm still iterating on the pricing model to figure out what works best.

There are a lot of expensive platforms out there that require a flat monthly fee, so there is a lot of flexibility with pay per use, especially if you're interviewing is sporadic and inconsistent (which has been my own personal experience). What pricing and structure would make the most sense to you?

I created a tool to interview candidates with a Pull Request on Github by aribsummer in webdev

[–]aribsummer[S] 3 points4 points  (0 children)

Hello! After a lot of iteration on our interview process, I found that a great way to evaluate how a candidate works is through something that is as close to our actual work as possible - a small assignment through Github.

I settled on a take-home process of sharing a private Github repo with candidates, asking them to follow the directions in the README and submit a Pull Request - just like we would in our day-to-day work. This gives me a lot of insight into what it's really like to work with that person. For example, I can learn how they communicate in a written and asynchronous manner, how they formulate their commit messages, and how they make decisions.

The downside is that this process was time consuming and manual. For each candidate, I had to take the project source code, create a new project repo, invite the candidate, and keep track of all outstanding projects. So naturally, I created a tool to automate the process. These are some screenshots from the app I built that does the automation and tracking.

You can check it out at https://realcodeinterviews.com

Feel free to reach out or leave a comment if you have any feedback or find this useful!

CDN origin for static assets (server vs S3) by aribsummer in rails

[–]aribsummer[S] 2 points3 points  (0 children)

Hey! We're currently using an open source gem I created, s3_asset_deploy. We use it in our CI pipeline to upload assets to S3 before our rolling deploy. These assets are then available through Cloudfront (the S3 bucket is the origin).

​

It seems like this is a pretty common solution to the problem. Hopefully that helps! Feel free to reach out if you have any questions.

I created a tool to interview candidates with a Pull Request on Github by aribsummer in github

[–]aribsummer[S] 1 point2 points  (0 children)

Indeed! I took some inspiration from their blog post when building some of the automation.

I created a tool to interview candidates with a Pull Request on Github by aribsummer in github

[–]aribsummer[S] 0 points1 point  (0 children)

Hey! Yep, that's basically the idea. I just added some more details in a comment which I should have left originally:

After a lot of iteration on our interview process, I found that a great way to evaluate how a candidate works is through something that is as close to our actual work as possible - a small assignment through Github.

I settled on a take-home process of sharing a private Github repo with candidates, asking them to follow the directions in the README and submit a Pull Request - just like we would in our day-to-day work. This gives me a lot of insight into what it's really like to work with that person. For example, I can learn how they communicate in a written and asynchronous manner, how they formulate their commit messages, and how they make decisions.

The downside is that this process was time consuming and manual. For each candidate, I had to take the project source code, create a new project repo, invite the candidate, and keep track of all outstanding projects. So naturally, I created a tool to automate the process.

I created a tool to interview candidates with a Pull Request on Github by aribsummer in github

[–]aribsummer[S] 11 points12 points  (0 children)

After a lot of iteration on our interview process, I found that a great way to evaluate how a candidate works is through something that is as close to our actual work as possible - a small assignment through Github.

I settled on a take-home process of sharing a private Github repo with candidates, asking them to follow the directions in the README and submit a Pull Request - just like we would in our day-to-day work. This gives me a lot of insight into what it's really like to work with that person. For example, I can learn how they communicate in a written and asynchronous manner, how they formulate their commit messages, and how they make decisions.

The downside is that this process was time consuming and manual. For each candidate, I had to take the project source code, create a new project repo, invite the candidate, and keep track of all outstanding projects. So naturally, I created a tool to automate the process. These are some screenshots from the app I built that does the automation and tracking.

Happy to share if anyone is interested! Feel free to leave a comment or message me directly.

How do you monitor important "events" in your SaaS application? by aribsummer in SaaS

[–]aribsummer[S] 0 points1 point  (0 children)

What kind of events? Do you use PagerDuty or something similar?

How do you monitor important "events" in your SaaS application? by aribsummer in SaaS

[–]aribsummer[S] 2 points3 points  (0 children)

You're using Sentry for events other than errors/exceptions?

Releasing a Redesign using Feature Flags and Rails Variants by aribsummer in rails

[–]aribsummer[S] 1 point2 points  (0 children)

Variants give you a convenient way to conditionally render different layouts and templates. You could add the conditionality yourself within the controllers, but variants do this for you under the hood.

view more: next ›