1,180 karma · joined March 8, 2007
If you're confident you're encrypting all your data, then you're still way above average. The nice thing about FDE is that I can "set it and forget it." I don't have to think about which files belong on which partition anymore. It's all safe.
It's easy to forget that the cloud is powered by real physical infrastructure, and that cloud vendors have maintenance needs too. AWS gave us a fair amount of notice about the reboots, and they've been understanding and helpful along the way. I'm willing to be understanding toward them too.
Do customers really care about the name brand or "warranty" of the SSL certificate? What percentage of customers are even aware of who issued your certificate, and do those customers really have concerns about StartCom?
This sounds like the argument we heard from DynDNS salespeople last year, about how our customers expect us to be using "enterprise" vendors, rather than "consumer-grade" vendors like Amazon Web Services. Even our savviest customers have never asked us who our DNS provider was.
(That said, they never aggregated this data across multiple websites, so I really don't get what the whole fuss was about.)
Let's say you have two servers, primary and secondary -- primary is the one that's currently acting as your load balancer. When both servers are running Heartbeat, they exchange UDP pings every second. If the primary server stops responding, then the Heartbeat process on the backup server will automatically take over the shared IP. When the primary box returns, it won't cause any problems or steal back the IP address, until you explicitly instruct it to do so. (If you really wanted it to steal back the IP automatically, I'm sure you could configure it that way.) You can also initiate a failover with a single command, which is useful when you need to do maintenance on the primary box. Running "/usr/share/heartbeat/hb_takeover all" is a lot simpler than having to manually reassign the IP address.
My company's infrastructure is very dependent on heartbeat -- we use it to support our load balancers and all our back-end services. You need to be careful or it will do "surprising" things when you're rebooting or changing the network config, but on the whole it makes it cheaper and easier to provide highly-available services.
Of course, if you're using a hardware load balancer, it should have a similar failover protocol built-in. I'd recommend just using its built-in features, that's what you're paying the big bucks for.
Most of our candidates came from Craigslist; we advertised in 3 cities and got quite a few candidates from all 3 cities. We also got a few good candidates from the monthly HN thread. We posted to a few inexpensive job boards like Startuply and Startups Hiring but we didn't get many responses. We haven't tried any of the more expensive job boards like GitHub and Stack Overflow because the ROI isn't very clear. Those sites are pretty expensive, especially with 3 positions open. I'd love to hear more from others about whether those are actually worth the money.
PBworks is hiring a Senior Operations Engineer!
PBworks is hiring a Senior Operations Engineer who can wear many hats. We're looking for folks who aren't scared of being hands on with everything. Willing to compile a grsecurity Linux kernel? Troubleshoot network packet loss? Scale databases? If you’re able to take on a wide range of responsibility, this position is for you.
Your job will be to create an environment where 4 million users and over 1.5 million workspaces can flourish and change the way people work. You'll get the freedom to do the job right, and a fantastic engineering team to back you up. What are you waiting for? Mail your resume and a short paragraph of why you'd like to join to jobs-ops@pbworks.com.
What You'll Be Doing:
- Physical server management: Managing a cluster of about 70 physical servers in San Francisco. Plus 3 servers in Sacramento. Plus a handful in our office in San Mateo.
- Engineering: Developing ops infrastructure tools in PHP, Perl, Ruby, or shell scripts.
- Automation: automating deployment with puppet.
- Monitoring: using Ganglia and monit to understand what's going on with the systems.
- Networking: Running the network infrastructure, including routers, switches, and site-to-site VPNs between the three locations above.
- Databases: Managing a handful of MySQL databases: advising developers on schema changes, keeping the databases reliable, and optimizing performance.
- Security: Analyzing the systems' security, keeping up with new threats, and recommending and implementing new security technologies and policies.
- Email: Ensuring the best possible outgoing email deliverability, and that we don't lose any incoming email.
- Office IT: running the office network; operating the employee VPN; occasionally fixing a printer or troubleshooting someone's laptop.
- Planning: Monitoring resource utilization trends; budgeting; planning for growth.
The Operations Engineer role is extraordinarily wide. If you've got software development experience, there are a variety of customer-facing infrastructure projects that may interest you. If you like NoSQL, there are definitely ways we can add NoSQL databases to optimize performance and developer productivity. We're looking for someone with a wide range of experience and interests, but if you haven't already worked in all these roles, we're here to help you learn.
Requirements: 3+ years experience running a production cluster. Debian and SaaS experience strongly preferred.
Bonus: Knowledge of PHP, puppet, git, quality programming abilities, computer science chops, and an understanding of SaaS business.
Technology: You'll get to solve real business problems with a wide range of technology. Here's a sample of what we work with: Debian Linux, Apache, Nginx, Percona Server (MySQL), memcached, MogileFS, XtraBackup, LDAP, puppet, Ganglia, monit, Perl, Node.js, ejabberd, Vyatta, Amazon Web Services, Solr, Postfix, git.
Why we're different: PBworks blurs the lines between operations and development. You'll sit in on every team engineering meeting and have input to decisions at all levels. As part of your job, you'll continue to architect our system to handle failures so you won't get paged when a hard drive fries. We're committed to providing the resources so that these failures don't become emergencies. We value automation and addressing the root cause of issues so they don't happen again.
To apply, email jobs-ops+hn@pbworks.com.
PBworks is hiring a Web Software Engineer!
We're counting on you to make a big difference in our product. It's not just an opportunity to make an impact at PBworks, it's a responsibility. Millions of people will be using your code.
You're a jack of many trades: you know your way around a Linux command line and Firebug with equal aplomb; Javascript optimizations and SQL optimizations (and when you shouldn't yet bother with them); the design of MVC frameworks and visual design with CSS. You know how to make something beautiful and approachable soup-to-nuts. You've coded a few projects of your own, maybe some of them have even made the front page of Hacker News, but you're curious to jump into an existing small team that actually has millions of users and do some real, helpful work.
Fluency in: HTML5, JavaScript, CSS3, JSON, jQuery, PHP, MySQL, git
Bonus for: node.js, Erlang, Perl, bash, Photoshop, Smarty, Prototype, mogilefs, memcached
You love: Agile, unit testing, functional testing, rapid prototyping.
To apply, email jobs-fwe+hn@pbworks.com.
PBworks is hiring a VP of Engineering!
PBworks is looking to hire a world-class VP of Engineering to direct, manage, and grow our engineering team at PBworks and join a great management team. Candidates should have knowledge and experience with Software-as-a-Service best practices and methodologies, such as frequent deploys, functional testing, and automated rollbacks. Candidates should have at least five years of management experience but still be active programmers with code-review and prototyping level strengths in a modern scripting language (such as Ruby, Python, or PHP) as well as fluency in modern HTML, CSS, and Javascript. Strong preference will be given for LAMP stack proficiency. Extra consideration will be given to candidates with experience hosting software for very large clients and candidates with UX skills.
Candidate should have experience building and executing effective agile product development and project management strategies, and continuing to build a top-notch, highly, innovative team. Experience with workspaces and team collaboration software in general and PBworks in particular is a strong plus. Master's in Computer Science preferred.
You'll be in charge of one of the most powerful, scalable, popular, and sophisticated hosted collaboration tools in existence: with over 4m users a month, hundreds of terabytes of user data, billions of recorded actions, and a million and a half groups. Our team is small but highly effective; every engineer in the group is capable of working on a wide diversity of projects - from low level systems debugging to SQL optimization, to best practices in modern Javascript and CSS. You'll be redefining the future of how our customers get their work done - everything from collaborative medicine to treat cancer patients to innovative creative teams shaping the next great TV commercial or videogame to university research labs, and even a few un-stodgy law firms.
We'd love to have you come help our team win and grow!
To apply, email jobs-vpeng+hn@pbworks.com.
Before applying for a job, I would want to check out the company's home page and see "do they look competent? Do they look like they're building a product that they're proud of? Is it something that I want to be a part of?" I'd also want to check out the company on LinkedIn or other social networks, to see if they're actually thought leaders in their community, and to see if I know anyone who can give some more color on the people involved.
It's a job seeker's market out there. You may be special, but if you don't tell me who you are, I'm unable to determine whether you're really special or not.
If you have multiple web servers servers in different locations, you might be thinking of "Geo-DNS" -- this actually directs the end user to the nearest web server. There are pros and cons to this approach, namely that the end user may be using an intermediary DNS server that's not actually very close to the user. For example, you might end up sending all Comcast users to your east coast USA server, no matter where in the USA they actually are. I'm not familiar with providers who offer this service, but here's a Server Fault thread on the matter: http://serverfault.com/questions/30567/geo-dns-providers
So, for example, say you're trying to fly to Chicago (ORD). The article's point is that it may be cheaper to buy an EWR-ORD-STL ticket, because there's actually more price competition when flying to St. Louis.
The whole dichotomy is silly. A tech business needs to figure out what to build, to build it, and to sell it. (Not strictly in that order.) Every one of those steps requires cross-functional thinking.
They also offer extended validation and other paid options. I use them for wildcard certificates, which are normally at least $200 each. I've created nine wildcard certs since January 1, for a total cost of $50.
A high-end chair will probably last for ten years, so you're talking maybe $100 per year. Compare that to the cost of regular massage, or chiropractic, or back surgery, and it's clearly a good return-on-investment.
But the Aeron isn't the only good chair around. I learned this back in 2006 when I was planning on buying an Aeron too. I stopped by a brick-and-mortar HealthyBack store (http://www.healthyback.com) to try out the Aeron, but I tried out the competition too. I wound up buying a Nightingale CXO chair instead. It wasn't as trendy, but it fit my body frame a lot better than the ones people usually mention online. It's important to do this comparison shopping in person, because our bodies are each very different and you need a chair that feels right for you.
I was an undergrad at a more traditional school where we registered for classes months in advance. I was amazed that the Stanford system was so informal, but in practice it worked just fine. It's wonderful to be able to audit a few classes before deciding on exactly what you're going to take; you may learn that you can't stand a professor, or love a surprising subject.
In a situation like this, I'd expect you'd need to convince an investor that (1) you have a sustainable competitive advantage against the big players, so they can't just take your idea and destroy your business, (2) your business model can generate enough profit to justify the outlandish capital requirement, and (3) you have the right team to make all that happen. #3 is a lot easier when you don't have such big hurdles with #1 and #2.