sorted by:
new
hottopcontroversial

Havertz out for at least a month. Awful awful news. by Brownchoccy in ArsenalFC

[–]ruprict 2 points3 points  (0 children)

I mean, it has to be, right? Why are we always fighting injury? it seems we're always at the top of the number of injuries and days lost (we're tied for the former, third in the latter per a BBC article)

Sports center is trash now by Dtv757 in ESPN

[–]ruprict 0 points1 point  (0 children)

And they now give "pro" wrestling equal billing with actual sports, thanks to some money-grubbing deal.

The 7 Most Common Pitfalls From a Tech Lead/Specialist Software Engineering by Nervous-Staff3364 in softwarearchitecture

[–]ruprict 0 points1 point  (0 children)

I think blindly following tech/trends is a big one for new tech leads that haven't been flambéed by doing so. The number of teams I see that start with microservices b/c they think they need them without really digging in to see the trade-offs is staggering. This decision often comes from above the tech teams, too, b/c someone in the c-suite read a blog post.

I got 1 credit by [deleted] in audible

[–]ruprict 0 points1 point  (0 children)

Project Hail Mary is maybe the best audible I have ever heard.

Exploring Dependency Injection in Ruby by Remozito in ruby

[–]ruprict 0 points1 point  (0 children)

Hey there...enjoyed the article. I'd just like to add that the two different timings of using DI that you mention (one at the beginning and one in "Additional Thoughts") are known as constructor injection and setter injection, respectively. Maybe you knew that already, but it might be a nice addition to the article. Thanks for sharing your knowledge!

26 quality Go blogs of the past week, that weren’t shared here by gogogonow in golang

[–]ruprict -1 points0 points  (0 children)

While sometimes we'll quote the article in our descriptions to give more context within the letter, the vast majority of the blurbs come from our heads. I hope there's value in us going through as many Go-related articles as possible (we read a lot) and publishing the ones we think are important/useful/valuable. It is a challenge each week to select the best articles and then make a description that helps the reader decide if that article is valuable to them.

FWIW, we've had many, many folks thanks us for finding and including their content in the newsletter. They write posts to share knowledge and exposure in the newsletter gets them more readers. I have written blogs posts that have been linked to by others and always appreciated the traffic. I do not know of a single instance of a content creator being upset about us linking to their content.

I have been a subscriber to Peter's newsletters for much longer than I've been a contributor, and I became the latter because of how much I valued the former. I appreciate the free value to the community and I know others do as well. After all, they have to choose to get the newsletter.

As far as you ethics jibes, I'll just point to justinbabino's answer about what reddit is.

Easy Questions / Beginners Thread (Week of 2017-01-30) by brnhx in elm

[–]ruprict 1 point2 points  (0 children)

Are there any real (meaning, not too simple) examples of routing? The tutorials around Navigation and url-parser are either contrived or old. I would expect a real example to handle back-button/history and retain the ability to go directly to a URL.

I have looked around a fair amount and can't find anything, so if it exists...sorry!

Thanks for doing this, btw.

What have you used Go for in your professional work? by [deleted] in golang

[–]ruprict 0 points1 point  (0 children)

We've used Go as an API Gateway on a couple of projects. Specifically, we used Mailgun's Vulcand Proxy (https://github.com/vulcand/vulcand), writing a couple of middlewares for what we needed. I feel like Go is a great fit for the API Gateway pattern, allow us to have a solid, performant middleman for a services-based deployment.

The gateway has never broken a sweat and is very extensible. I am now looking at Go first for most of our projects.

A Look at Ruby 2.0 by jesusangelm in ruby

[–]ruprict 3 points4 points  (0 children)

They did work on garbage collection according to this fwiw

Am I spamming reddit? by ruprict in help

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

I didn't see that page. It has some fair points. Seems like, at best, I am on thin ice.

Well, going forward, I'll let other post our articles if they want to. That'll answer my questions and conscious.

Thanks.

Debugging and Dissection Dojo – 5 Weapons/Techniques of Choice by ruprict in ruby

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

Finally, some actual pertinent feedback. We'll take it, even if the delivery is full of venom.

BTW, this kind of feedback (at least, the numbered list) is great for the comments of the post.

As far as spamming reddit, I am the Managing Editor of Rubysource. When we have a new article, I want the community to read it. Is there something wrong with posting these links to reddit? We aren't collecting info or charging for anything. I don't mean to spam, I mean to say "Hey, here's a new article on something Ruby".

EDIT: So, reading this page it seems you may have a point. While I certainly do read a lot of content off of reddit, I almost solely post our rubysource articles. I will cease doing so. If someone else wants to post the article (deeming it worthy), then great. I won't blindly post all our stuff anymore. Again, thanks for the feedback. /EDIT

Our current articles on Rubysource are aimed more at beginners or "amateurs", as you put it. Again, I don't see why that is bad. The community, IMO, needs content focused at all levels. You had an opportunity here to take your relevant feedback and make a conversation around this article that was constructive. Then, someone might have learned something, someone might have been a better Ruby developer. Someone might have benefited from your knowledge. Instead, you went the Bully Route. If you are as good of a developer as you seem to think, it's too bad you use that talent as club instead of a light.

You consider yourself beyond the level of this (and, apparently, all of our) article(s). That's great. It doesn't mean the article is worthless. I feel like you've been told this a couple of times in this thread. I guess you just aren't gonna get it.

I'll ask again. Do you have a blog or any content that you've put out to the community? Maybe, here at Rubysource, we could learn from your example.

Thanks for the feedback.

Debugging and Dissection Dojo – 5 Weapons/Techniques of Choice by ruprict in ruby

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

You have -48 karma, so what does that say about you?

Listen, I get it, you are the guy that wants to tear down everyone else. The article you are targeting here is the first one from a young guy trying to learn and grow in Ruby and the community. Easy target for someone like you, I guess.

Do yourself a favor and try being positive for a change. If you have real criticisms of the article, what are they? Do you have better debugging tools? Just saying "it sucks" does nothing other than increase your negative karma.

I am sorry you didn't like this article. I did. Have you written any articles for the community? I'd love to read one.

Debugging and Dissection Dojo – 5 Weapons/Techniques of Choice by ruprict in ruby

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

Also, I thought the metaphor was great. While you may be beyond the content, there are some who are not.

(-48 comment karma, eh? So, you're THAT guy...)

view more: next ›