Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: What did you work on in 2017?

news.ycombinator.com

Post reply on HN
Print view View original

101–110 of 583 posts

Re: Ask HN: What did you work on in 2017?

#101

Post by ploggingdev »

Hosted Comments https://www.hostedcomments.com/ , a Disqus alternative with a focus on privacy. The learning experience of building Hosted Comments was great : using iframes to embed comments in websites, building a commenting system with voting and some features which Disqus does not have : locking comments, hiding comments (not yet deployed https://imgur.com/a/R89Cw ). It started out as a sideproject, then decided to go the SaaS route and now a little confused about whether I want to pursue this as my main project. I'm thinking about releasing an open source self hosted version and continue offering a managed service.

Bored Hackers https://www.boredhackers.com : a public chatroom based community site. Think of it like reddit, but chatrooms insteads of forums. I just deployed the first version a few hours ago. Bored Hackers is an experiment at building the community site that I wish existed : public chatroom based communites, pseudonymous users, transparent moderation logs, an open source code base and a site that is welcoming to non-technical users. Currently, there is a single chat room for all discussions and support for user created chat rooms will be added shortly.

Re: Ask HN: What did you work on in 2017?

#102

Post by jacobwg »

javajosh wrote: post #79
jacobwg wrote: post #73

I left an amazing company with one of the best work environments ( https://webflow.com ) to work for a non-profit that fights child sexual abuse ( https://www.wearethorn.org ). The work has been incredibly rewarding, and although I was quite nervous about leaving an awesome job and jumping into an unknown, in hindsight almost everything about the change was a meaningfully positive improvement. Working towards a missi…

I had an opportunity to work for them but declined because I didn't want to look at the content. Tell me: how much of that do you have to actually go through? And to other devs: if you have thick skin and an iron stomach, go work for them.

It’s definitely a factor to be aware of. We are legally not allowed to be exposed to image content, as developers, but personally I do have some exposure to text content as part of my role. Thorn has an excellent support / wellness system, with professional counselors, in place though for proactively staying healthy and processing what exposure we do experience.

Re: Ask HN: What did you work on in 2017?

#103

Post by city41 »

alin23 wrote: post #100
city41 wrote: post #83

Earlier quoted context omitted.

I just recently joined Spotify. I have found their "we will play similar music after your music ends" feature to enable me to discover lots of new artists. I find it interesting you found Spotify lacking here, because I am finding the opposite.

I'm a long time Spotify user. I love that feature too and it worked very well for me when it first launched. But after a while it started playing the same songs that I have already heard many times. Spotify's algorithm is very unpredictable so I can't say it will work out the same for you. But if it will, at least you can have another try with what I'm trying to build ^_^

Gotcha. That makes sense. I could see how over time that feature gets less useful. Looking forward to trying your tool, if you have a website or mailing list for it, please share.

Re: Ask HN: What did you work on in 2017?

#106

Post by tootie »

I spent most of the year working my ass off consulting for one of America's most hated companies building an utterly pointless system. My only consolation is knowing that I wasted a ton of their money since there's no chance it will pay any returns.

Re: Ask HN: What did you work on in 2017?

#108

Post by flowardnut »

learned RESTful apps in Ruby, Sinatra, and sequel.

built an api wrapper in Python serverless for our ecom website.

trying to smooth out the api for the new react frontend we built. imagine a 10 year old java api where every endpoint is extremely different and behaves in magical ways (or not at all) if magic cookies are present.

nightmare.

Post reply on HN