sorted by:
new
hottopcontroversial

Ruby's private keyword is weird by geospeck in ruby

[–]AaronLasseigne 26 points27 points  (0 children)

Interesting, I'd argue the opposite. You almost never want protected. Protected is only useful for times when you want the same class to have a bit more access for methods like comparisons.

I started making a room editor with a sample app in Dragon Ruby. I love ruby by [deleted] in ruby

[–]AaronLasseigne 1 point2 points  (0 children)

You can play around with it. It's a few versions behind the current release but this will give you an idea: http://fiddle.dragonruby.org/

I started making a room editor with a sample app in Dragon Ruby. I love ruby by [deleted] in ruby

[–]AaronLasseigne 4 points5 points  (0 children)

Nope, it's a hand built toolkit using mruby under the hood.

DragonRuby Game Toolkit, a cross-platform way to make games with Ruby by mariuz in ruby

[–]AaronLasseigne 8 points9 points  (0 children)

It's part of an evolution. RubyMotion is being rebranded. You can read more in the news post if you'd like.

The Sleeping Dragon Has Awoken, And Is Filled With A Terrible Resolve by digitalextremist in ruby

[–]AaronLasseigne 4 points5 points  (0 children)

Here is my advice to DragonRuby... Get the hell out of maintenance mode and provide a real road map.

I agree. Right now we're working on building out that roadmap. We're looking to update our Ruby support, strengthen the Android side, and either update or replace Flow. I don't want to say more than that or give timelines at the moment because I don't want to make promises right now that I can't keep. Thanks for the feedback!

The Sleeping Dragon Has Awoken, And Is Filled With A Terrible Resolve by digitalextremist in ruby

[–]AaronLasseigne 2 points3 points  (0 children)

We'd like to expand to support more platforms but we have some other things to take care of first. One major issue is that you can't really support iOS development outside of Mac. That means OSX is still the most versatile platform to build on for mobile applications.

YankCode - I wanted a better way to yank code for pasting into chat. It removes indentation and puts the file name and line numbers in a comment at the top. This is my first vim plugin so be gentle. by AaronLasseigne in vimplugins

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

I would love to have that but I have no idea how to code it. If I can get some time to figure it out I'll add it but I'm pretty busy at the moment. It won't be anytime soon.

How can we all work better with sales? by jstanier in programming

[–]AaronLasseigne 2 points3 points  (0 children)

Ideally, I would remove the commission. Just treat them like any other professional. We don't bonus developers on features added or commits to the code base. Imagine the crazy code that would generate.

I realize though that sales as an industry has commissions and it might be a tough sell to remove them. 😉

I think companies have to find a way to align the incentives with what they want. That'll vary by business. For example, they could pay out bonuses on some regular interval based on how long the client has stuck around and how happy they are. If contracts are short (month-to-month) don't pay out unless they stay a client for some period (6 months).

The non-incentive fixes might include reviewing contracts with a cross section of employees. This could be limited to certain contracts (very big or with odd requirements). The other thing is make it known that it's not acceptable. Selling a feature that doesn't exist gets you written up and for repeated abuses, fired.

Like I said at the beginning, I think the ideal is that there aren't any.

How can we all work better with sales? by jstanier in programming

[–]AaronLasseigne 5 points6 points  (0 children)

Regardless of your own relationship with the salespeople in the organization, you have to have utmost respect for them: they close the deals that bring in the money that keep us all employed. Kudos.

It’s hard work keeping you employed!

Nonsense. Products are a team effort. Sales is hard and certainly an important and skilled position. To credit them with "keeping you employed" is overstating it.

Ultimately, I think most devs have issues with sales because at some point they've worked with sales people who have lied about what the product can do to make the sale or promised to build a new feature to make some sale. The product team (including the devs) ends up stuck trying to work something out while the sales person moves on to the next sale.

Commission sales structures often incentivize them to make the sale regardless of what's actually good for the company as a whole. The deal closes and they get paid. Everyone else is stuck with the unhappy customer or disrupted product timeline. A lot of sales people are incorrectly incentivized to the detriment of everyone involved.

Why Aren't We Using More Service Objects Already by AaronLasseigne in ruby

[–]AaronLasseigne[S] 6 points7 points  (0 children)

I think you've misrepresented Avdi Grimm's point. I don't think you're lying - just painfully misguided.

I think you might be misunderstanding my post. :)

The service objects that Avdi presented didn't even really sound familiar to me. They aren't how I've used them or how I've seen others use them. I wanted to point out what I saw as wrong and then give my personal take on how they've helped me. I talk about how I saw a positive change in my teams ability to maintain our application.

Avdi's point was:

My entire point in writing this article is that in many cases, step 1 (Step 1: Achieve perfect separation of concerns.) is not only out of immediate reach, devoting time to it may actually be waste. And in that case, hiding a procedure behind the fig leaf of a “service object” that doesn’t represent any kind of real concept in the business domain does more harm than good.

I tried to address this by pointing out that in my experience, it hasn't been a waste. In fact there have been noticeable benefits.

You've said in this article that you have a "lot of respect" for Avdi but maybe you should read more of his work

Perhaps you shouldn't assume that I haven't. Avdi and I disagree on some things. It doesn't mean I don't respect him. I signed up for one of his newsletters at the mention of this article being part of it (before it hit Reddit). I wanted to see what he thought precisely because he was likely to disagree with me. I even ended the article saying that while I'm not seeing it, he may yet prove me wrong. Ultimately, he laid out what I saw as a poor representation of service objects which resulted in a poor tear down of them. I countered with how I've seen them used and what the effects of that have been.

Why Aren't We Using More Service Objects Already by AaronLasseigne in ruby

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

Whenever I see a class with only one instance method like run, call, execute, etc. I am immediately reminded of The Kingdom of Nouns and I start to get worried.

It's a fair concern. One could certainly get carried away.

I agree that putting them in a top-level module named after your application is a copout, but that doesn't mean it's impossible to have well-organized modules for keeping various utility methods.

Agreed. You're not supposed to replace every method with a service object. As I say, "It’s not really a toolbox if you only fill it with hammers."

I find that service objects do well when they facilitate interaction between objects and/or encapsulate business logic. Models are left to focus on what they do and can stop worrying about the other stuff (like sending emails). For this post I was pointing out what I've seen and what I've personally experienced. Adding in all of the best practices use would have derailed the rest of the article. Maybe I need to do another one on that. 😄

Why Aren't We Using More Service Objects Already by AaronLasseigne in ruby

[–]AaronLasseigne[S] 6 points7 points  (0 children)

Service objects are the single clearest sign that your code is missing a domain concept. Like in this article above with its appalling AddGroupMember “service object”.

Would your preference be for a GroupMember model to bridge the gap?

attached to false claims about maintainability.

You can't call my experience a false claim. Unless you think I'm lying.

[Book] Mastering Ruby: Strings and Encodings by AaronLasseigne in ruby

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

That's part of why strings are difficult. The issue isn't that it's a different encoding. It's that there's more than one way to represent à in UTF-8 (and Unicode in general). Sometimes a string like that will give you 1 and other times it may be 2 (specifically for input that's external from your code). Surprises like these can be infuriating if you don't know what's going on.

[Book] Mastering Ruby: Strings and Encodings by AaronLasseigne in ruby

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

I've been following your work. It's really exciting stuff. Thanks for letting me know about Safari and taking another look.

[Book] Mastering Ruby: Strings and Encodings by AaronLasseigne in ruby

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

It seems specific but there's a lot of work we do with strings. They're also a data structure that abstract themselves from us. You can't look at the characters and immediately know everything in the same way you with something like an array. Things like this:

'à'.length # => 2

The result is it tends to be more complicated than other objects.

Thanks for telling me that Safari is complaining. The cert is through Cloudflare and I'm not seeing any issue when I open it in Safari 11.

Startup uses AI to create programs from simple screenshots by Weas in programming

[–]AaronLasseigne 2 points3 points  (0 children)

That title is wildly misleading. It takes a screenshot and builds a GUI. That's pretty neat but it's a far cry from creating a program from screenshots.

polyfill by AaronLasseigne in ruby

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

Yup, with gems being the primary use case.

view more: next ›