If you find meaning from digging into low level libraries, that's great. Most people would think of meaning as having shared values with the business you're working for and it's end users / customers. Prioritize finding end-users who you genuinely care for and whose lives you want to improve is one way to find meaning.
I'm a huge fan for space-based games and these screenshots remind me of Freelancer (2003). Really neat.
It's not just a CSS theme though. The XControls/Xcomponents libraries are complex toolkits.
There are actually two products: XControls.org, which augments IBM Domino XPages and also XComponents.org for an Angular.js environment.
This is one of those open source tools that I'd love to see mature into a commercial offering: emailing request tickets, getting bugs fixed, having access to frequent release candidates, etc. I emailed them awhile back asking for commercial license and inquiring about any support they could offer. They're open to the idea, but seem very new to the game.
Begin with a problem then start with the thing that your users will see and work your way down the stack. New students enjoy the immediate gratification from changing a color, moving things around on the browser, or animating a great looking turtle. I recommending having a problem to work within as it provides constraints and a set of mini goals. "I need to take user input" then becomes "I need to process user input" then becomes "I need to put this user input somewhere" and once your friend visits each part of the stack, he can decide where he wants to spend time.
I didn't answer the "fun" part because it's not so great a leading indicator of career direction. Both sides have significant depth and breadth in terms of technical challenges and skill.
This isn't accurate at all. 1) AngularJS was not built by Java developers at Google. Further, it's not clear if the original authors were Java developers. 2) JSF was built by the guy who created Struts, which he did to because he was unhappy with how Struts worked. 3) I wouldn't describe JSF as a Java/XML framework, it's intended to be a component framework.
If I'm not mistaken, access to these videos previously required an account from a GV-funded company. It looks like they've opened up content to everyone. Very cool.
I wrote something like this a few months ago.
Depending on Google Spreadsheet for uptime monitoring is nothing more than just a fun hack. I'm surprised that some people here are taking it so seriously. If you're using a script like this, then I hope it's just to keep those single dynos from falling asleep :)
It's also subject to Google Docs availability, my script sometimes fails to run with only a "We're sorry, a server error occurred. Please wait a bit and try again." email notification.
Anyone know the mechanics of what's involved with auditing and graphing CSS sizes with Graphite? What's instrumented and when is it logged?
I agree. At first glance there's a lot of shorthand (@, =, ^, ?, &) but that knowledge comes with time. I experienced a lot of confusion with the compile() and link() functions that I feel could have been prevented with better docs. Until that's done, I recommend the path I took: lots of experimenting and watching John Lindquist's videos over on egghead.io.
I like it. Today, I saw copy.com's landing page and really enjoyed that too. Bootstrap without being bootstrap.
Good comparison. Thanks.
What's the difference between this new support and the nginx-push-stream module? https://github.com/wandenberg/nginx-push-stream-module
I'll +1 this.
The startup scene is definitely growing in AZ. There are plenty of interesting people doing interesting things. The low cost of living, increasing number of awesome meetups, and growing co-working community is a pretty good sign of things to come. I've met passionate entrepreneurs at almost every corner of the state. Just off the top of my head--Flagstaff has NACET; Tucson is leading the open data movement; Chandler has Gangplank; Phoenix has CO+HOOT & SeedSpot; Mesa has a wonderful Hackerspace; and Marana was recently elected a top digital city in 2012.
That said, there's room for improvement. There aren't a lot of people with experience investing in hi-tech (lots hi-tech military stuff, but not the hi-tech that HN normally discusses); as a community, we don't have really good marketing muscle; there are few veterans willing to recycle capital; and not a lot of foreign direct investment because people have this impression that folks from AZ are crazy.
I love that place though. You can live in a goddamn mansion for the prices you pay in SF.
Funny you ask, last night, I got Wordpress running on Heroku.
https://github.com/mchung/heroku-buildpack-wordpress
Why? For the lulz.
Nice write up.
Want to add two other reasons we're horrible at making estimates.
1. Expectations. 2. No widely accepted language for writing requirements.
Re: 1. Expectations are just hard to manage. Even when you do get "So the site's pretty simple" - the set of features in their brain is totally different from the set of features in your brain. Alas, it'll take more than "all it needs to do is X, Y, Z" to fix this process.
Re: 2. Is there a professional software consulting company that has solved this problem? I say there isn't. I also say that with the advent of Agile/Lean Startup methodologies, it'll probably never happen - "No, we don't write reqs, we have stories you need to approve." uh huh, okay. For writing requirements, I got really damn fond of Cucumber, but then the lean-ux took off, and that shifted everybody's priorities.
Bottom line, until there's a widely accepted way to communicate design and functionality, making bad estimates will always be easy to do
Thanks for writing this paul. From time to time, it's important to recognize the things that truly matter.
Any examples of library-in-app in the wild. I get the idea, but want to know what this looks like in practice.
Mounting engines or Sinatra apps? Creating a new gem to for extractable functionality? Just curious about what this looks like under the hood.
Let me share some quick thoughts and trade offs.
I did:
(1) Cloned bootstrap into the Rails.root/lib/assets directory, setup config.assets.path, added the require lines to my css and js files.
Alternatively I could have done:
(2) Used one of the gems mentioned in the comments, added the require lines to my css and js files.
In 2.0, there's some manual work involved to get the js pointing to the correct image path, but assuming you've made it that far, those changes are pretty simple to automatically regex.
IMO, the biggest difference is the way you go about styling markup. In (1), markup is modified intrusively. The example from the OP can be tolerated. But now imagine if all your divs had a .row or .spanxx classes attached. If that's unacceptable for you, I'd find a gem that you can work with.
I was tracking 2.0-wip for a couple of months and it wasn't easy to stay up to date with all the changes. Hopefully it's getting easier for gem authors to track and update
This is great. Thanks.
Workaround is to start an experiment. http://www.google.com/experimental/
Very happy to see that Phoenix, AZ made the list.
I've been using GitHub since 08 and I still think it's refreshing to continually run into developers that have recently discovered the distributed (hell, rejuvenated!) approach to collaborative software development.
Welcome.
I was young, but I remember the cover of Time magazine very well.
For fun, I dove into this recently. The only strong opinion I have is for Rails projects to ship with Cucumber as means for acceptance testing. Here are a few good Rails projects which satisfy that.
* The Rails Dev Directory: http://github.com/engineyard/rails_dev_directory/
* Spree: http://github.com/railsdog/spree
* And Gemcutter: http://github.com/qrush/gemcutter. Gemcutter also uses Gemfile.
* Fat Free CRM: http://github.com/michaeldv/fat_free_crm. It doesn't use Cucumber, but it's still good code.
If you want to get setup with Rails 3.0, check out this gist I wrote: https://gist.github.com/50be644a99ff372d5b1f
They should have waited till the end of the year to make this call.
I bet there are a bunch of users who were waiting till October to buy a phone at the discounted rate. That's 24 months after the original G1 was released, which is when those owners are eligible for discounted upgrade.
Like myself.
I haven't read the remarks, but I think it's possible for people with a lot more experience than I do to make that sort of assessment and be spot on.
It helped me.
One day, with any luck, I'll be able to look back and make the same remarks. Hopefully it will be because I'll be a lot better at it by then.
Powerpoint isn't the problem. It's a symptom. The real problem is communicating effectively with ideas/pictures.
There are two books which have made me better at this:
1. The back of the napkin [http://www.thebackofthenapkin.com/]
2. Slide:ology [http://blog.duarte.com/book/]
These books kick-started my journey to understanding (and appreciating) the use of diagrams, colors, fonts, and imagery for the purpose of conveying an idea.
Update: Added links.
I'm certain you would gain an appreciation for this if you knew exactly how tricky hyphenation detection is.
Lovely!
I actually did something similar..
Last year, I started looking at algorithms to count syllables. It turns out that hyphenation and syllable detection have a lot in common.
Anyway, long story short: one of the approaches I use on Haikuist is a hyphenation algorithm.
I'm glad you built softhyphen.com. It's such a fun idea.
(http://haikuist.com: poetic micro-blogging for haiku lovers)