i agree with this. also, one annoying nugget is what happens if the api owner changes the logic behind wanted/most and they breaks some functionality behind something i've built?
I think something interesting and related is the ability to sacrifice personal activities for a project. I've tried working on projects with many friends that just could not sacrifice part of their weekends with their girlfriends to do work. Or they were "too tired" after their day job to work on side project but could play video games. Some people won't even sacrifice some sleep!
Every few months people start an argument about post vs put vs patch and versioning in the url vs some header. I think a lot of developers aren't fully aware of PATCH and making put actually fully replace an object can be dangerous. This probably especially bad if you use some schemaless db. For versioning, I like to support both. Let the user do what makes them happy. Not really that hard to support URL and header...
I am like Dr Hibbert, I chuckle at inappropriate times. But my point was just because something is popular, doesn't mean it is the best for everything. And that you _should_ understand how things work under the hood and not just choose these platforms blindly. I am not specifically hating on RoR, I feel that many developers choose it just because it is easy and popular without understanding what rails gives you and how it works.
I get a little chuckle when I tell people I am building some app and they ask "Why aren't you using RoR and MongoDB?" Maybe I am not comfortable with them in production?
I've experienced that at other hackathons too. Fake click throughs using photoshop drawn screenshots beat out actual mobile applications with backends. I stopped going to hackathons after a powerpoint beat out my hack. It was a cool idea but the only execution was drawing some pictures. 24 hours to draw pictures. Yup.
Agreed, the one time Amazon needed me to migrate an instance they told me when they would forcibly stop / start the instance and allowed me to do it before hand. How did you set up screen on EC2? I've had problems with it in the past but got it to work pretty well recently.
Zend is kind of bloated and tries giving you the world when you only need a form parser. require_once is also "slow" because it checks the list of required files each time you call require_once to make sure you aren't requiring the same file twice. It makes sense to stay away from that with a framework like Zend where it just wants to include so many files. With your typical app, not using require_once and only using require probably doesn't save much time
There is a good reason to not include the closing tag. Silly people can add newlines after the ?>. That leads to random newlines in your output which are annoying to track down.
Hehehe so true. We use some odbc driver at my company and it had major memory leaks / seg faults. I had to compile debug versions and test it out to figure out what was going on. That being said, some PHP modules are really great and would be hard to live without. I need mysql, memcached, apc, json_decode, etc... I guess the extensions I've written myself I could rewrite to some hip hop spec?
I really like trello. Something about it feels so natural. I like it a heap better than jira + agile plugin. I do like pivitol tracker too, but trello can do more.
I've been there. I think the idea is to look for people who can "solve problems" and can use the right algorithm for the right problem. In the end, it seems that candidates just spend a lot of time practicing algorithm problems in online competitions to get good at the questions so that they can recognize the base problem in interview questions and implement answers really quickly. Just because you've been spending hours doing online competitions and remember algorithms really quickly doesn't make you a good engineer in my book. Especially when you will probably forget all of them the second you get your job and stop practicing.
I can't blame other people for studying for tests, I can just blame the tests.
Made me think of a recent stealth startup that somehow got a few hundred thousand signups before it launched... and then it launched... and failed. Went through a waterfall release process, and failed some more =/
Im not a RoR developer, so forgive my ignorance. But how does this keep happening? I thought ActiveRecord is a mature product by now. I hear about these types of bugs happening with RoR pretty often, is the "magic" of ActiveRecord and hiding SQL from the developer really worth it? I wonder how many RoR developers even understand what SQL injection actually means.