Skip to content

Instantly share code, notes, and snippets.

View oscarlaf03's full-sized avatar

Oscar Ortiz oscarlaf03

  • São Paulo
View GitHub Profile
@wrburgess
wrburgess / gist:3778949
Created September 24, 2012 22:54
Setup wicked_pdf and wkhtmltopdf with Rails 3 and Heroku
@ssaunier
ssaunier / user_binding.json
Created December 3, 2017 21:10
Sublime Key Bindings for using Emmet inside Babel JavaScript files. Sublime > Preferences > Key Bindings
[
{ "keys": ["tab"], "command": "expand_abbreviation_by_tab", "context":
[
{ "operand": "source.js", "operator": "equal", "match_all": true, "key": "selector" },
{ "match_all": true, "key": "selection_empty" },
{ "operator": "equal", "operand": false, "match_all": true, "key": "has_next_field" },
{ "operand": false, "operator": "equal", "match_all": true, "key": "auto_complete_visible" },
{ "match_all": true, "key": "is_abbreviation" }
]
}
@kevcha
kevcha / assets_in_rails.md
Created September 3, 2018 07:48
Assets in rails

How assets are handled in Rails

What's assets ? Assets are all javascripts, css, and images files. They are stored in app/assets and app/javascripts.

The directory app/assets is handled by a tool called sprockets that we want to change in future. The directory app/javascripts is handled by another tool called webpack.

Why we have 2 directories with differents tools ?

Historically, we used only the directory app/assets for all javascripts, css and images files. Sprockets was used to apply some transformation on all those files.

module.exports = {
env: {
browser: true,
es6: true,
jest: true,
},
extends: [
'react-app',
'airbnb',
'plugin:@typescript-eslint/recommended',

What Hiring Should Look Like

This is definitely not the first time I've written about this topic, but I haven't written formally about it in quite awhile. So I want to revisit why I think technical-position interviewing is so poorly designed, and lay out what I think would be a better process.

I'm just one guy, with a bunch of strong opinions and a bunch of flaws. So take these suggestions with a grain of salt. I'm sure there's a lot of talented, passionate folks with other thoughts, and some are probably a lot more interesting and useful than my own.

But at the same time, I hope you'll set aside the assumptions and status quo of how interviewing is always done. Just because you were hired a certain way, and even if you liked it, doesn't mean that it's a good interview process to repeat.

If you're happy with the way technical interviewing currently works at your company, fine. Just stop, don't read any further. I'm not going to spend any effort trying to convince you otherwise.