Esparta @esparta@ruby.social

@brian_kephart currently there's a PR trying to document Concerns[1]:

> Concerns are a way to make large controllers or models easier to understand and manage

That's the thing I see the most and the worst use case. Refactoring using Concerns is the wrong approach, but people follow the practice as a mantra.

Splitting your 4K lines controller into concerns is fixing the wrong issue (god object/classes) with the wrong methodology & tools.

[1] https://github.com/rails/rails/pull/39766/files

@brian_kephart I wouldn't say modules vs concerns are inferior or superior to each other. When using as a mixins they're actually the same & it's fine. If you aren't using their specialized dsl, just use module, but people use concerns anyway.

A "better" organization via clases (OOP), services, modules, DI, containers, or even rails engines would be have better results IMO. When using all of them correctly you don't even need concerns. Using just MVC-Concerns limit your systems.

AppSignal: To concern or not concern

https://blog.appsignal.com/2020/09/16/rails-concers-to-concern-or-not-to-concern.html

After 6 years of using Rails I'm still not sold of use concerns to simplify mixins.
Surely has their use cases but there's definitely better ways: containers, dependency injection, abstractions, or even plain modules.

"It's a concern when you start using Rails' concerns"

New live coding of https://exercism.io with #ruby track: Matrix

This was particularly nice to do with #TDD & memoization

https://twitch.tv/videos/7272912

Continuing #ruby track at https://exercism.io : High Scores

https://www.twitch.tv/videos/723256151

Besides #TDD, I was exploring #OOP & Array methods.

You may not be aware of this, but there's a lot of coordinated efforts to a better documentation of Ruby core classes & the standard library.

People like Burdette Lamar, Eric Holden (drbrain) and others has been nailing it going method by method doing a better docs.

Today Jeremy Evans proposed a "Method Documentation Guide" for this:

https://github.com/ruby/ruby/pull/3999

It's really nice to see this happening, if you are privilege enough to help, please do. The ruby ecosystem need your help.

@james looks like it fix itself days after I toot about it.
The other account was @esparta and I was not able to see the posts from there.

Thank you.

Not sure how I got into this, if you can help will be highly appreciated.

I'm trying to Boost of a toot I did in other mastodon instance, but through the clients (web and @Fedilab) , but I'm not seeing this toot on that profile:

https://fosstodon.org/@esparta/104434340461986629

Is it related to this instance or the Fostodon instance?

What I see is an outdated list of toots shown in the image.

Thanks!

cc @james

From time to time developers create error messages that are curious and scary.

This is from Octopi, a GUI front-end to pacman, the #ArchLinux package manager:

[aborted]: Suspicious execution method

the explanation is buried on their website:

https://tintaescura.com/projects/octopi/faq/

>That’s because you need to run Octopi, Octopi-Notifier and Octopi-CacheCleaner using their full path commands: “/usr/bin/octopi”, “/usr/bin/octopi-notifier” and “/usr/bin/octopi-cachecleaner”.

👻🔥💻

Yesterday I did an streaming about CS Fundamentals with TDD approach (test first, code later).

-- Binary Tree #1 (insertion)
https://twitch.tv/videos/543697779

I was using #ruby, #rspec and my old friends #vim and #tmux

It's far from perfect, but hope it helps.

2020-01-19 - Late hacking session with #ruby Standard Library

https://www.twitch.tv/videos/538913018

This session covers Oct 2019 to Jan 2020 changes on Standard Library gems.

I added a Privacy page to my website:

https://esparta.co/privacy/

Privacy (and security) is something I do really care and would love everybody else join the effort to protect ourselves.

It's highly inspired on what @kev did for his own privacy page.

Your opinion is important, let me know if you have any questions about it :)