http://gizmodo.com/5989263/groupme-now-lets-you-split-the-bi...
645 karma · joined October 16, 2011
http://gizmodo.com/5989263/groupme-now-lets-you-split-the-bi...
When I left my first job that had a generous but still limited vacation policy, I got a nice sized check paying me back for my unused vacation. I never felt like I was restricted from taking vacation and I definitely liked the money that actually ended up paying for the week off I took between jobs.
Agreed with the point about security. We have a public part we want to make into a general KB but also a private part for internal. If anyone comes up with something, I'd love to see it.
Lastly, because what comment wouldn't be complete without some sort of "criticism" on someone else's awesome, hard work, what prompted the decision to use the /* */ commenting for page-specific config? In my experience (maybe this is just because I've used jekyll too much) it seems that Yaml frontmatter is pretty typical for .md file config.
I'm pretty aware of it.
Definitely awesome that people are trying to optimize in the devops space but just not sure I could be convinced to switch to something that isn't at least somewhat mature.
Yep, this. I work in a place that after a merger got rid of the creative director and replaced it with an "everyone is senior" approach. While it's nice on paper, we have no accountability, no one to set or drive standards, and no review process other than client sign-off. I think we would benefit greatly from a Director or VP or some sort of management that could authoritatively say "this is what we're doing and this is how we're doing it".
I've been toying with the idea of getting my own setup but wasn't sure where to start. This definitely clarified that it's pretty expensive to get started so I may just stick with the artisan coffee shops in town.
Instead of Compass, I've switched to using Bourbon (bourbon.io) but may consider just using Auto Prefixer in future dev efforts.
Source maps I can live without since I haven't gotten used to them. I know it's in the works or at least being thought about: https://github.com/hcatlin/libsass/issues/122.
I'm not usually one for hackathons but definitely do like to spin up mini app ideas and just tinker. I'll give it a shot!
Also a great plug for Jekyll in general. While there can certainly be more worrisome factors than cost for a site, site performance should be one of the most important issues when launching. By completely getting rid of a backing database, page lookup times can be reduced dramatically. As Prose continues to mature, it's getting more and more flexible by the day. Just last week they implemented an extensible "tagging" feature for posts: https://github.com/prose/prose/issues/464.
In case you haven't noticed, I'm a fan. Kudos to dev seed and big props to the White House team for the willingness to move away from Drupal.
I think the spirit of this is great but "mass protest" might be a bit of a misnomer.
Now, as the author pointed out, Firefox seems to be unable to keep up in some key areas.
I think you'll be pleasantly surprised to find that not all sites built with Bootstrap follow the default mold of a thin 100%-width black navigation bar across the top with white background. Sure, there are lots that have that layout, but as developers learn more about Bootstrap, the sites that use it as their underlying framework are definitely diversifying.
I'm slowly but surely getting better at design things but I choose to focus my energy on development rather than prettifying pixels (I say that with absolutely no intent of malice).
I agree that broadening my skills to include design would be helpful. I'd also be really great off if I learned how to treat my own ailments and fix my own car. I can't do it all though, so when I have the need, I partner with designers. I look through portfolios, gauge talent and ability, and hope for the best.
If you're building games or working with a team who does, I'm going to guess you're working with fairly edge functionality in browsers where javascript support is great. If you're building sites for clients who are still (sigh) using IE7 internally, you just can't get away with something quite so simple.
As another commenter mentioned: "Even the most avid follower of JS updates can't compete with a team of the standard jQuery draws upon. When a new method gets rolled in to the core of jQuery, something that speeds up selectors for example, your code improves without you doing any work."
This is the same reason I use a library for preprocessing my CSS. I'd rather update a gem and trust a team whose focus is processing CSS than try to rely on myself for keeping up to date with the pace of the CSS WG and browser vendors.
Also, for anyone wanting to dig around the jQuery source, James Padolsey made a great tool for it. I know I was pretty amazed to find out just how much is going on under the hood. http://james.padolsey.com/jquery/#v=git&fn=
:)
I'm curious what shop you are thinking of that has this kind of time breakdown? I know that in my previous agency (political/non-profit/corporate consulting), the team responsible for emails spent hours and hours working on crafting perfect subject lines and meaningful content. The subject and the content drove the design.