Have you asked them why they are started to writing a code in first place? Maybe, since it's a programming interview, they thought you are trying to measure their theoretical knowledge than their practical day to day knowledge.
You should probably reword your question and give a hint that a candidate can use any available tool. If it's a programming interview my first instinct would be writing a code, if it's a sysadm interview I would use available tools in the system.Context is important...
Nice work. But I wonder how they handle table alterations, I couldn't see they mentioned on the docs. Is it possible at all? If it is, since pg_shard doesn't support transactions, what if alteration fails ?
Table alterations are not supported: if we're missing this in our docs I'll be sure to make that more explicit. They're certainly in the list of things we'd like to support.
At the moment, our customers who do need table alterations accomplish them by using a script that propagates such changes to all worker nodes.
NOT related with their ssl campaign but : What are the other trust able alternatives to Namecheap?
I love them but after they "updated" their design, every time i try to buy/renew domains I'm having nervous breakdown :
* It's impossible to find what I'm looking for.
* Facebook style panel menu ( I don't know how they calling it ) makes only sense on tablets/phones, on desktop it's just pain...
* New design uses screen real estate really bad. My screen filled with big buttons, big texts and senseless images... Information that I'm looking for is lost between them.
* Gray text on white background... Not so readable...
I mostly use Namecheap, because, well it's cheap ;) (and also a good service). But for the domains I really care about I use https://www.pairnic.com/index.html . PairNIC provides free phone support staffed by technical folks (during business hours in Pittsburgh, PA). It's $19/year. And I use http://www.gandi.net/ for the esoteric TLD's.
I've had good experiences with name.com, price and service -wise ... the frontpage isn't as slick, but once logged in the UI is nicer. Have yet to see a registrar with an actual good interface though :|
I recently tried out badger.com, and I like their UI. They have a demo of their UI you can try before buying. They also offer some nifty built-ins like automatic Heroku integration.
I am also looking for a new registrar since Moniker has turned in to a shadow of it former self. First, the customer support took a nosedive. Now, they redesigned the site and its a mess.
The Namecheap redesign is also a bit messy. They have a mix of the old design plus some new interfaces. Also, we've been waiting for ages for them to implement 2 factor authentication and when they finally do it, it's an SMS only solution that's no good for those that are without constant coverage or need to travel outside the country.
This probably isn't quite what you were asking, but for DNS hosting, I'm enjoying PointDNS[1]. They give you unlimited records for one domain, which is all I've used to this point. But their rates seem quite reasonable, so I'd be happy to pay them when I have the need.
Biggest downside is that they don't support many advanced DNS features such as Anycast, GeoDNS, and DNSSEC.
http://www.namesilo.com/ is my go to go for cheap .coms. I don't know about their support (never needed it) but they're fast, support 2fa and, well, are cheap :)
ssls.com is another trusted alternative...and it's owned by Namecheap with a different design.
Curious - are you still encountering those issues? That may be from the initial launch in January but we haven't heard about this from others. We definitely appreciate the feedback though.
I experienced similar issues this weekend while trying to register a new domain. Once logged in, my immediate impression was that I should click the "Domains" dropdown from the white navbar to manage my domains. The actual links I need are hidden behind the expanded menu, it would be nice highlight these options better since they're the primary use case for logged in users.
The only other issue I've noticed is a large disconnect between the new aesthetic of the landing page (which I quite enjoy) and the yet-unchanged UI of the dashboard.
Yes they are actual issues : I had to renew one of my domains today and I'm really frustrated with the UI. I also realized I didn't checked namecheap for a while because I had same issues when i used namecheap last time.
I don't know why others didn't reported UI issues but in my case : Opening a support ticket didn't seem to be a good option, it was an UI issue and wasn't related to billing or some technical problem.
Why people wants to believe it works ? Well, it has nothing to do with religion. Reason is same as using robots for manufacturing : It's cheap, fast and could be 7/24 on duty.
Why these devices haven't tested properly ? Easy, corruption (, which is not condoned by any religion)
It doesn't necessarily need to be corruption. If the device just makes random beeps or something then it's easy enough to be convinced that it's correlated with how close it is to explosives.
People do not automatically think of doing a blind test and measuring the results and seeing how well it correlates with actual bombs.
* Any folder in your project can have index.html and indeed it should have.
* Parent talks about static pages, not about rails-ruby/php/python project.
But i get your point : If somehow somebody screw with servers config, there is a risk to expose your apps files & configs. You can follow parents advice but set your root path in apache/nginx config to /var/www/www.example.org/public instead of /var/www/www.example.org
Even a static site can be structured so that the .git directory is outside of the main public mount.
This gives you a natural place to store notes, documentation, and other non-public content.
It's not about screwing with the server config, it's so that it takes several stupid mistakes before your .git folder is flapping in the breeze, not just one. Being one configuration directive away from embarrassing failure is not a good idea.
> Being one configuration directive away from embarrassing failure is not a good idea.
I can't stop but thinking about PHP webapps, for instance Wordpress serves wp-index.php in the same directory as wp-config.php, indeed only one configuration directive away from blowing it all up in your face.
I would guess it's a configuration error around something like smart extensions, maybe? "If the clean URL has a .xml at the end, send the request through PHP."
Dumb, but it's the only thing I can come up with offhand.
There is too much options [0] and it's more flexible than it should be. I know , it sounds weird but with bootstrap all you have is 12 columns and when you have less options it's easy to plan.
Maybe the other problem is : Units are not in multiplies of 5 and that forces you unnecessarily to think. If it would be in fixed units like bootstrap or in multiplies of 5 ( pure-u-3-25 etc.) i would be less thinking while deciding the length of some div.
I know static page generators are more cool and nerdy but there is a wordpress plugin called really static[0]. This plugin can generate static html files from your site. It can save html pages on some folder or upload via ftp.You can install wordpress on your laptop or some password protected sub-domain, buy some nice looking theme, start publishing and enjoy having best of the both worlds...
Ok, i'll play devil's advocate : Windcatcher works as same principle as evacuation slides on planes and even if it's about physics i think it's somehow ( design ? ) patented.
So, what about patents ? Is there any patent that product violate and may cause later any problem ?
Say it's the exact same mechanism as evacuation slides.
Patents in the U.S. since 1995 have had a term of 20 years, prior to 1995 it was a term of 17 years.
The slides were initially patented in 1956. In 1956 the U.S. patent term was 17 years; those patents expired in 1973.
But, let's suppose some advances were made and the specific valving mechanism was patented later. It would have had to have been invented and patented some time after 1995 to still be covered by a patent.
If it were patented any earlier, its term will have expired and the idea is now in the public domain, which means anyone can use the idea without paying anything.
They should really add some info about patents and prior art on kickstarter page. And i hope , just to be sure , they applied for a patent their design.
Even if they did, applying for a patent doesn't indicate that you have a valid patent, nor does it provide any protection whatsoever for patents that came before.
As others have pointed out in this thread, existing products already use this mechanism. It would be very difficult to patent something that was very obviously invented already.
It always makes me sad when a new product arrives and people start worrying about patents. I can't believe there are people who still believe that patents encourage innovation.
I understand the advantages of using these tools but isn't it too much ? Node, Npm,Yeoman, Grunt, Bower just to bootstrap some font-end code, if you don't use node.js for back-end you have to use other tools in back-end development too ( composer, phpunit, gem, rake etc... you name it... ). Sometimes i feel like we use tools just to use them.
edit: Just to clarify : I'm not saying don't use any of them and don't organize/automate tasks and code like monkey...
You are right, it's a lot of tools for FE development. However, (IMHO) when I used this toolkit, I felt very productive, for example, if you make a change in the CSS, the UI is automatically refreshed (no need to manually refresh). The final build process optimizes PNGs among other things. All in all, it felt that someone has thought of everything that a webdev needs and put it in.
Could you explain what you mean by 'no need to manually refresh'?
I understand this to mean you don't need to refresh your browser to see the changes you've made in your source.
EDIT: Ah, nevermind - just read up on it: "Our LiveReload watch process automatically compiles source files and refreshes your browser whenever a change is made so you don't have to."
You should probably reword your question and give a hint that a candidate can use any available tool. If it's a programming interview my first instinct would be writing a code, if it's a sysadm interview I would use available tools in the system.Context is important...