gurgus

Doing the weekly food shop over the last 12 months has felt reasonably nuts. For the most part, we usually get the same stuff each week (fruit/veg/meat/dried food etc...) and it's gone from being about £100 to almost £170. Fruit and veg prices in particular seem really crazy.

This looks like a really neat tool but I wish that people didn't have to sign up in order to submit a response to the survey.

Blame culture isn't the way forward here.

Do a post-mortem, work out root causes, work as a unit to ensure this doesn't happen again.

Obviously if there are levels of gross negligence or misconduct discovered during post-mortem, that will need to be dealt with accordingly, but coming into this with an attitude of "we must find someone to blame and incur repercussions" isn't healthy at all.

We are humans - don't forget that.

edit: forgot some words.

There's a typo on the main page: "Collect the partecipation quote" <-- should probably be "participation"

I just tested this out on my website and it worked exactly as instructed which is always a plus. Super easy to set up and a clear set of analytics :)

That's something similar to what I've been doing lately where I've been trying to use colour palettes I like from other sites in my own designs but it's so hard to get the feel right... This is probably why design is its own full-time job!

Sweet username!

It's in a browser. It's browser based.

> - Signal and Whatsapp, as others have pointed out, are far from being comfortable as being private (they already know too much, phone number, etc.), and don't have the convenience of a browser based app.

Whatsapp does have a browser based app. web.whatsapp.com

If you're in London, hit me up! I work for a mid-large company that is full of Scalia devs. We'd be more than happy to give you an interview :)

It's a really cool read. I thought it was neat and a bit more elegant than doing something similar with Window.postMessage (https://developer.mozilla.org/en-US/docs/Web/API/Window/post...).

Yes! I absolutely love magic wormhole!!!

This is pretty sweet. Very simple and the code base looks pretty easy to follow. I should get some time this evening to submit a PR to add a couple of small things :)

Very cool writeup. I love posts like this that cover random things like this. I'm definitely going to take this away and mess around with it!

This is super awesome work. Well done - you should be proud!

I have to admit, I remember stumbling across your comment when you accepted the challenge and in my mind I scoffed, thinking you were never going to do it. Boy was I wrong! Once again, this is super cool.

Cool project!

Makes me want to think of another fun way of crowdsourcing stock tips for fun.

Maybe something like TwitchPlaysWallStreet?

For an intern, that is insanely good.

edit: In fact, for a lot of people, that is insanely good! Apologies if I came across as an asshole when I said "for an intern".

That classic "well, nobody else has had a problem, so you must be the problem" response.

I remember at one of my first jobs, myself and another programmer were working on a side project (outside of work hours, not using company resources in any way) that were considering monetising. Our contracts stated that the company we worked for owned all of our code produced in and out of working hours.

We got to the business end of the project and decided to consult our workplace to find out how strict they were on this. The conversation with HR went something like this:

> Us: Oh hey there, can you clarify clauses X/Y/Z in our contracts regarding ownership of code. We are working on a project we are planning on monetising at some stage and we need to know if the company is going to do anything about this. Our project has no conflicts of interest and we haven't stolen any IP of the company.

> HR: Oh... We've never had a question like this before... We can't say exactly. We'd have to consult our lawyers.

> Us: Cool - can you consult them and let us know what they say, please?

> HR: Sorry, we can't consult them as they charge by the minute and it's too expensive to warrant a conversation with them.

> Us: So... you're not going to answer our question.

> HR: Exactly. You'll have to do it at your own risk.

Awesome response - are you able to give me an example of what you mean "wrap third party components"?

Thanks :)

Was looking for this comment! CircleCI is amazing. We use it and it seems to offer us everything we need in a very nice shiny box.

This isn't a useful answer for you at all, but I thought I'd mention that there are "kind of" innocuous eval()'s such as Angular's eval() [1] where instead of JS being evaluated (which can lead to nasty things), an Angular expression is evaluated, which is a bit safer.

Obviously what I've just said doesn't help solve any problems here, but thought I'd throw it in there anyway :)

[1] https://docs.angularjs.org/api/ng/type/$rootScope.Scope#$eva...

Come on guys...

C64 all of the things!

Some of the comments here are ridiculously negative or taking away from the fact that Jeff has done something cool here.

Good stuff, Jeff! Keep on doing stuff like this and don't listen to the hate/negative comments.

I think hackernews and reddit would be fantastic, to be honest.

How much machine learning is actually involved here? Or is it more static data analysis?

Love the idea. What sort of social networks does it monitor? Do you have per-site specificity? For example, I might want to post at a popular time on Reddit, but only at peak/popular times for specific subreddits.

https://blog.goeswhere.com/2010/04/java-cpp-polyglot/ here's an example of the same sort of thing but with C++/Java

All fixed up now. Thanks for the feedback :) I ended up setting __proto__ directly so that an instanceof test passes.

Thanks! Will update my post and attribute you with that!

Interesting - how can I go about this?

Late to the party but I'll just add in my $0.02

I remember the best interview I had was at a company offering open source software. For the coding components of the interview they give applicants a task (they cherry pick one of the easier ones) from their JIRA backlog and told applicants they've got two weeks to come up with a patch. It didn't matter if the applicant could fully solve the bug/feature, since it's not particularly fair to expect the applicant to be familiar with the ins and outs and gotchas of the system they are working with, but what did matter is that they A) submitted something, and B) could talk their way through their thought process and how they arrived at their current solution.

This sort of process really clicked with me. Obviously it's not as straightforward for some organisations that may offer proprietary software, but the process could certainly be adapted for a lot of organisations, in my opinion.

Wow awesome ideas! Also thanks for the bending ideas too - it would definitely help make things much easier on the eye too!