Kiba VS Picnic CSS

I started https://github.com/thbar/kiba#kiba-etl to scratch my own itch & be able to write properly structured ETL jobs in Ruby. It was a blank-slate rewrite of something larger (activewarehouse-etl) which I could not maintain anymore.

This landed me not strictly a job, but long term consulting gigs with a number of companies in EU, UK & US.

The job was directly related to the project: companies wanted the expertise of data engineering & ETL, often with Kiba directly, but also in general.

This "side project" was totally worth it :-)

Definitely! As a matter of fact, this is the default data structure I use when writing Ruby ETL code (e.g. https://github.com/thbar/kiba/wiki).

Methods like "except" (https://docs.ruby-lang.org/en/3.2/Hash.html#method-i-except) or "fetch" (raising an error on missing key) are very convenient to write defensive data processing code!

Similarly, in Elixir, I use Maps a lot for the same type of jobs (https://hexdocs.pm/elixir/1.15.4/Map.html), with similar properties.

Ruby has a very cool ETL library named Kiba that fits wonderfully with Ruby's strengths.

Though it might be overkill for your problem, but have you had a look at [kiba-etl](https://github.com/thbar/kiba/blob/master/README.md)?

Kiba

If you don’t use Kiba, but work with data, check it out.

This was about 10 years ago, where there was Bootstrap, Pure CSS and little more, so I published:

https://picnicss.com/

It went to the front page of Hacker News (https://news.ycombinator.com/item?id=8315616). At the time I was a student in Spain doing coding just for fun, so any job-related opportunity would be slim and with really bad pay (I had actually already worked a bit as a dev for a pittance).

Someone contacted me and offered some really fun freelancing projects for what at the time seemed like an absurdly ridiculous large amount of money, so much that I got a great designer friend involved and split the money so the project would be even better.

I learned many things from that and as my curiosity pumped me to keep learning. I read about cases of people making 500k+/year as "normal" devs (meaning, not managers, and also not famous). Most of my Spanish peers didn't even believe that existed at the time, and thought I was crazy believing those "obviously fake" blog posts. But I've been working for USA companies basically since then, and couldn't be happier/wouldn't look back.

Picnic CSS:

https://picnicss.com/

My own and one of the older ones, almost 10 years ago, see the original Show HN:

https://news.ycombinator.com/item?id=8315616

Added support for Picnic CSS

2. Picnic.css

franciscop/picnic - 👜 A beautiful CSS library to kickstart your projects

I've disabled Issues in some of my more popular but end-user libraries and I couldn't be happier. Specially notorious was a CSS library[1] where many of the issues were on the level of "hey can you give me the code for X" or "how do you do X" where X was a general CSS question and not related to the library at all. I've received a bit of hate when I closed some of my repos issues as a PR [2][3]:

> If you spot a bug or any other issue you may go to hell because this software is officially Bug Free(TM).

> part of offering these to the public through open software is maintaining them and allowing feedback from users.

> It seems umbrella.js project suffers the same desease.

I've noticed there was a strong push around 2016-2018 to recommend newbie programmers NOT to go to Stackoverflow, but instead to ask the questions straight in the Github issues. Turns out, the problem was low quality questions and not the medium at all, and that just converted an issue that StackOverflow had solved long ago into burnout for open source developers on Github.

There's so many entitled developers out there that will come and demand changes. Github needs to step up their game and give authors more powerful tools. It might make new devs feel less welcome, but the balance is tipped way too much to allow anyone to create massive spam for projects right now.

[1] https://picnicss.com/

[2] https://github.com/franciscop/picnic/pull/203/files

[3] https://github.com/franciscop/picnic/pull/202