But, yeah, having just gone through a round of interviews I think there's a big range of quality at work in these, and passed on some companies because of how irrelevant their prompts were or unstandardized their processes were.
Does anyone know the rationale for creating Nixlang? Guix's use of Scheme proves there isn't a novel feature unavailable elsewhere, so it seems like a lot of wasted effort to implement a language that will likely only ever be used for one suite of programs. (And tooling; though almost none exists now, making the choice even more expensive.) I've tried to find one, but "nix" is a difficult thing to google for given the couple decades people have used it as a catchall term for unix and unix-like operating systems.
Spam from gmail's smtp servers. There are a number of spam services oriented towards small business. Their users are required to use their own gmail credentials. MailShake and FunnelBake are two services from my inbox this week, though they're deliberately hard to identify - no note in the headers, no footer on the email, customers encouraged to set up domains aliasing "unsubscribe" links, etc.
This is a growing source of spam for me personally and services I've worked on that have public email addresses (eg. support@), especially if near a mailing address. (Other services scrap lists of "local" businesses and sell them to the end users of the spam services.) Blocking gmail smtp is a non-starter due to popularity, graylisting doesn't help, and I haven't been able to find anywhere they take spam reports; search results are overwhelmed by discussion of reporting spam as a user of GMail.
I believe only once has someone who invited a problem user been banned. That inviter contributed a feature to disable invitations and was unbanned. But I think the possibility also has a deterring effect that prompts people to exercise care.
I'm not aware of one, but the Lobsters codebase with very similar functionality is available if you'd like to start one: https://github.com/lobsters/lobsters
You can get help in #lobsters on Freenode. If you know Rails, deploying to Heroku is an afternoon job; using the provided ansible scripts on a bare VPS is a day or two.
10+ years of experience with Rails development, mostly helping startups launch as a consultant. I've spoken at RailsConf and several other conferences, and written a book on Ruby. I also have significant experience with devops automation, React, Python, and mentoring junior developers.
I have availability for part-time work and maintenance retainers. Not available for strict management roles or pager duty.
https://push.cx/consulting or peter@ that domain. I care most about understanding your business's goals and helping you achieve them, so please tell me about what you're working on. Thanks! :)
I knew Nix came before NixOS but was interested in both for the possibility of managing servers. I'd have made significantly less progress starting from Nix.
I can see how Guile would be an improvement over the Nix language, but have tapped out my patience on related topics for a while.
The search engine broke, too. Maybe it's it's having a negative term like "javascript -npm" or searching only a single subreddit, but changing "www" to "old" in the url often takes a search from zero results to hundreds.
And that's on top of how much slower it is, how it starts with a sidebar covering the page, janky lightbox scrolling, fixed headers covering the page, autoplay everything, etc. Search and other major features don't work.
SQL isn't a good match for the recursive structure of comments (and our version of mariadb from LTS Ubuntu doesn't support recursive common table expressions), so the app pulls all comments in ActiveRecord objects and threads/sorts them there. It's expensive and uncached. Codebase is here if you're curious: https://github.com/lobsters/lobsters
Traffic counting has to wait until I have spare attention, which is also a shallow resource pool. :)
Lobsters sysop here - we're having trouble keeping up with YC News's level of traffic. We're not going to crash, but the unicorn worker pool is small enough that lots of users are getting 500s. I'm adding some caching.
The full report plays a lot of games to produce these striking, misleading graphs, like comparing yearly numbers with total values of all future pension liabilities at face value instead of any attempt at NPV. If you're curious to spot more, the 1993 edition of How to Lie With Statistics chapter 7 ("The Semi-Attached Figure") and 9 ("How to Statisticulate") are a lighthearted read.
I tried to evaluate it last month. Their login page does some kind of cross-site cookieing or referering that my privacy settings don't permit. Any time I log in, I get a warning that someone's been trying to brute force my account and it's been locked for 24 hours.
Support was useless. I was repeatedly asked if the IP address I gave them was public or private, when they should've had training or tooling to know at a glance. The help system closes tickets aggressively, ignores replies, and the link to keep a ticket open just leads to a knowledge base. Eventually support agreed to take a curl that reliably reproduces their bug, but I got no tracking number or even a vague promise they'd get back to me when it's fixed.
I concluded that if the product was broken and support was broken, there's probably something upstream in the business that's broken and I am not confident I'd be able to restore data.
I also do this, and also start talks asking people not to post photos of me online.
Also, I don't believe he's kept his picture off Facebook. Unless he avoids all photographs, one of his friends has posted a photo, and another of his friends has tagged him. It doesn't matter how many times you ask people not to post/tag, Facebook has very aggressively marketed this as a normal thing to do. The tag step probably isn't even necessary if he's consistently one of the only people untagged in a group photo.
I look forward to GPDR enforcement and hope it can be used to delete even Facebook's shadow profiles.
They still have your face from scanning your friends' photos and contacts. Combine datestamp, location, messages, and posts over years and Facebook knows who was together for a photo whether or not you've uploaded any or been tagged. Facebook knows the face of everyone who is on Facebook or who knows a few people who are.
But, yeah, having just gone through a round of interviews I think there's a big range of quality at work in these, and passed on some companies because of how irrelevant their prompts were or unstandardized their processes were.