andrew93101
That's the opposite of what I'm describing. I'm describing making something that people don't find compelling, that doesn't solve their problems, but they use it because it's their only option (the network effect).
If users generally dislike facebook, but continue to use it, it's a bad situation to be in for Facebook. It indicates that people are using the product because of its network effects and despite the product itself.
It means that if anything begins to actually challenge the network effect of facebook, they will be in a very tough spot.
- it encourages premature scaling
- many large businesses have lost the ability to innovate and lost the ability to respond quickly to market changes.
Both of those consequences can be fatal for a startup.
This is because last mile internet access is a textbook Natural Monopoly: http://en.wikipedia.org/wiki/Natural_monopoly
* Appfolio is looking for great full-stack engineers to deliver products customers love using Ruby, Rails, Javascript, Coffeescript, MySQL, CSS3, and HTML5. Currently hiring for Software Engineer, Senior Software Engineer and Principal Software Engineer *
We have small, high caliber teams developing easy-to-use solutions for our customers, and are looking for experienced level Software Engineers to continue our rapid growth pace. If you enjoy building from back-end to client–side in an environment that values shared responsibility and continuous learning, apply today.
Responsibilities:
● Develop scalable, robust, and simple web-based solutions to solve complex business problems
● Formulate, implement, and evaluate algorithms and database queries to support SaaS scalability and stability.
● Implement new features and optimize existing ones to drive maximum performance
● Research/share/recommend new technologies and trends
Knowledge and Skills:
● BS, MS, or Ph.D in Computer Science or related technical discipline
● 5+ years experience developing web-based applications, preferably in a SaaS environment
● Web development experience with proficiency in a modern programing language (Ruby experience highly desired)
● Creativity, ability to solve complex problems without a roadmap
● Experience working across all levels of the development stack preferred
● Experience with Agile/Scrum software development processes preferred
Ruby Mixins & ActiveSupport::Concern
The more I read on PRISM, it seems that PRISM itself is a minor revelation (that being, PRISM just automates what used to be done manually).
Most of the outrage just flows naturally from the Protect America Act, which was never a secret. The public is just now hearing about how the act is used in practice.
Also, routing exceptions using git blame isn't about placing blame on individuals for defects, it's about automatically managing and routing the massive quantity of exceptions that can occur in a large rails app with many users and many developers.
Most readers won't know svbtle, and of those that do, most won't think it adds any gravitas to the post. If I find a link rated highly on HN, that rating is the gravitas, not the blog's theme.
I don't know what state the author was in when he was working for Sony, but California State law prohibits such arrangements in employer agreements (Labor code section 2870):
http://www.leginfo.ca.gov/cgi-bin/displaycode?section=lab...
2870. (a) Any provision in an employment agreement which provides that an employee shall assign, or offer to assign, any of his or her rights in an invention to his or her employer shall not apply to an invention that the employee developed entirely on his or her own time without using the employer's equipment, supplies, facilities, or trade secret information except for those inventions that either: (1) Relate at the time of conception or reduction to practice of the invention to the employer's business, or actual or demonstrably anticipated research or development of the employer; or (2) Result from any work performed by the employee for the employer. (b) To the extent a provision in an employment agreement purports to require an employee to assign an invention otherwise excluded from being required to be assigned under subdivision (a), the provision is against the public policy of this state and is unenforceable.
Don't make your users wait for Garbage Collection
Predictable, Reusable, Maintainable and Scalable CSS
From speaking to other companies in our position, it sounds like there are no good solutions on the market currently. We unfortunately plan on building our own solution in-house.
In my mind, a business that excludes the time spent by its founder from its expenses is not honestly assessing its profitability.
The cost of commercial rent is minuscule when compared to the cost of engineering labor. If a business believed doubling floorspace would genuinely increase productivity by even 10%, it would be a no-brainer financially.
If you're working primarily alone on difficult engineering problems, with well-defined specifications and a clear division of who owns what part of the code, then (from my experience) solitary offices are more productive. Communication doesn't need to be as high-bandwidth, and concentration needs to be deep.
On the other hand, there are many environments that are different. If your organization intentionally has low-fidelity product requirements, the cost of communicating with business stakeholders needs to be low. If you intentionally eschew code ownership, engineers will frequently be working in areas of the codebase they haven't worked in before and need to talk to colleagues who know it better.
Open plans make concentration harder and communication easier. Closed office plans are the reverse. I think no office plan is "better" than the other, but rather our office plan should fit the work style of your organization.
Come work for us.
Each paragraph is more difficult than the last:NCCSBYVB VF N ENCVQYL RKCNAQVAT NAQ JRYY-SHAQRQ PBZCNAL SBPHFRQ BA QRYVIREVAT GNETRGRQ FBSGJNER-NF-N-FREIVPR FBYHGVBAF GB OHFVARFFRF. BHE PBZCNAL JNF SBHAQRQ OL N GRNZ BS GRPUABYBTL YRNQREF JVGU ZNAL LRNEF BS RKCREVRAPR QRIRYBCVAT FNNF NCCYVPNGVBAF. JR ORYVRIR GUNG N FZNYY TEBHC BS CNFFVBANGR CRBCYR PNA QRYVIRE RKGENBEQVANEL ERFHYGF. JR ORYVRIR VA...
If you are trying to really quickly get code in front of users, and are working through a lot of ideas that don't end up going anywhere (code that is eventually thrown away), then heavily tested code is probably not the best use of your time.
Once you get a product with some traction, and are going to be working with a codebase for some time (especially a code base that will be growing), heavily tested code is invaluable.
Example: Upgrading a large Rails app (~250k lines) from rails 2.3 to 3.0 in eight weeks. Having roughly a 1:1 code:test ratio allows us to be extremely nimble. It also allows developers to work in almost any area of the codebase with confidence.
For apps that will be around for awhile and will be growing, a large test suite is indispensable.
As a result, no browser controls: no back, home, or url bar. The window is dedicated to a single site.
And now on Lion, I can make anything fullscreen if I want to get rid of the OS chrome also and focus only on the content of the app/site I'm using.