sriharis

nilenso | developer | bangalore | http://nilenso.com, remote, online

nilenso is an employee-owned software cooperative based out of Bangalore, India. We're looking for people we'd really like to work with, across all experience and expertise levels.

This is my talk from euroclojure, 2016.

Here are the repos with the synth code, and the scrapers: https://github.com/ssrihari/ragavardhini, https://github.com/ssrihari/kosha

Here are the slides, although they're not all that useful without actual music that goes with them: https://speakerdeck.com/srihari/making-machines-that-make-mu...

Strangely, pulling from and pushing to github works. Just that no page on their website loads.

A common solution to conserve bandwidth is to use compression. This can be done easily in PostgreSQL by using ssh tunnels and turning on compression. I wonder why they didn't try that.

Slides for the talk above: https://speakerdeck.com/srihari/on-the-building-of-a-postgre...

Here the video of a talk I gave with the slides above: https://www.youtube.com/watch?v=OzoyRv_7fEk

^ answers all questions.

Sweet! Looking to angularize it?

Most of the CSS methodologies today, OOCSS, SMACSS, and now MCSS address the organization and maintainability of CSS. And all the examples they quote, pertain to large codebases. What I'd like to see and learn, is a methodology that details refactoring CSS iteratively as the codebase grows.

The fuzzy search is broken. "ck" doesn't match "LeChuck", and "mal" matches "Herman Toothrot".

Here you go: http://learnlayout.com/

This first lesson was quite similar to Clojure in fifteen minutes: http://adambard.com/blog/clojure-in-15-minutes/. I find both pretty good, although this seems more promising. Waiting for more!

See http://csscomb.com/about/. I think the order is configurable. Sorting helps readability and it helps you find the properties easily as your eyes get tuned to where they are usually found.

It's pretty cool that they have plugins for editors and IDEs.

Here's more on dashes and hyphens: http://practicaltypography.com/hyphens-and-dashes.html

I submitted this because I don't understand how so many people haven't even heard about this yet. This is a masterpiece on writing good CSS. I'll even go so far to say it is "The Right Way" to write CSS.

It is not the frameworks that are bringing about the change. http://oocss.org/ and http://smacss.com are bringing about this change. Bootstrap's CSS techniques are written with a heavy bias on OOCSS, and by doing that it is setting a good example. I'll give you that.

That is so true. Github had a lot of performance issues in their diff pages and they solved by using one-to-one mapping class-names and keeping the specificity as low as possible. Here's more on that: https://speakerdeck.com/jonrohan/githubs-css-performance?sli...

I think http://smacss.com is what you're looking for.

Although the context of hierarchy is useful in CSS, there isn't a need to specify the styles with the hierarchy. That increases the specificity as a side-effect, which is a bad thing for maintainability. SMACSS suggests showing the hierarchy in class names instead. For example: use .main-dialog-heading{}' instead of '.main-dialog .heading h2 {}'.

Edit: I actually wrote a detailed blog post on it: http://sriharisriraman.in/blog/2013/09/08/dont-nest-css/

Endorsed! I am also a SMACSS fan. And I say "Keep the specificity minimum" as a mechanic to write more maintainable and scalable CSS. I also have another mechanic - "Don't nest CSS", and here's my explanation for why: http://sriharisriraman.in/blog/2013/09/08/dont-nest-css/

I don't what about this is semantic except the class names. But even that comes with a heavy loss in maintainability. If I have to customize say, the border radius of an icon button, I'd have to override this specificity: `.ui.vertical.labeled.icon.buttons .button:first-child > .icon` Not cool.

People use radio-button questions to reduce the effort required by the mass to take the survey, thereby increasing the number of responses. In my own experiences, lesser people fill in text boxes. I find that asking open ended, non loaded questions works when talking to them face to face or over a call, but not over an online survey. I'd like to know how text based online surveys fare.

An open source Wufoo :) Cool.