Hacker News new | past | comments | ask | show | jobs | submit | robinwarren's comments login

That's really cool to hear. We used to make use of the toy library in Bristol when we lived there, it was a great way to get toys the kids could play with for 2 weeks then return them when they got bored :)

I did a lot of listening to the griefcast (podcast with comedians talking about people they lost) recently which I think helped me. No idea if that's good advice and the people on it skew heavily uk centric so you might not know any of them. Good luck!

The plan at the moment is to use this as a lead magnet for our main (paid) tool https://www.bluecatreports.com/

But, possibly we will discover some need for features we could add to a paid version of this in future.

I think this was a deliberate move from the Trello team not to implement this. They were very much focussed on the "not developers" market and didn't want to implement features which were mostly only of interest to a developer audience. It seemed to work quite well for them commercially :)

I think swimlanes is a feature that benefits everybody, not just developers. At a most basic level, swimlanes by assignee would be crucial for a family board (as opposed to coloured cards by assignee, since colours could be used for category of task, etc.).

So I used Trello at home, and Jira at work. I loved how fast Trello was (despite being Electron); it’s still probably the fastest Electron/web app.

But the lack of swimlanes pushed me to Favro, which was too slow to enjoy using. When Atlassian bought Trello I figured that swimlanes would never arrive, since they wouldn’t want to eat into Jira features and market share (which i disagree with, but I digress).

As a result I use Trello casually and for simple projects with my wife, but didn’t go all-in on it. I’ll give this Power Up a try though!

Trello don't allow any more fine grained access than this. Power-ups can request view and write access and that is about it. No way to say we only want access to the current board or etc. Or that we only want to be able to update labels/members but not add comments.

They have been talking about changing that, but I understand it is complex and never really becomes a priority

It would also be software dev 101 for an organisation of AWS's size and clout to do some pretty basic things - If someone's costs increase drastically (ie spending in 24hrs what they spent in the last year or etc.) then maybe flag it up to them - If the above is combined with costs on services/regions they've not used, definitely maybe contact them? - If the above is combined with a well known exploit used on compromised accounts, again maybe contact them?

Not saying the OP has no responsibility here. Just that I don't think it is that black and white. There is plenty AWS could do to avoid this sort of thing happening. Totally fair to call them out for that. Especially when the cost of phoning support is $2-3k specifically because of the new costs on your account!

Note, I think, you also need to be GDPR compliant for EU users when they are not in the EU. So I don't think IP blocking actually works for 100% of cases.

I would suggest not getting too hung up on this, it is showing you the worst outcome and assuming you have made a good effort to be compliant I should think things would be fine even then. No doubt you have Ts and Cs, that document is full of clauses put in place because of things like this, and any of them could probably result in a worse letter from a customer wanting to sue you over something. But I image also that hasn't happened to you yet either?

> I think, you also need to be GDPR compliant for EU users when they are not in the EU.

What you think does not align with my understanding of the GDPR, what makes you say this?

Fair enough, I did read this somewhere but it is obviously wrong now I check it out. Thanks!

> Note, I think, you also need to be GDPR compliant for EU users when they are not in the EU.

No, location is what matters. Of course one could argue if IP is a reliable indicator of location, given VPNs, potentially faulty GeoIP databases, ...

Geoblocking EU users makes it fairly clear you don't intend to serve[0] them, at least in my opinion. If the only reason you could be in scope is offering your service in the Union, and you do your best to avoid that, you should probably be out of scope.

We'll see what the regulators think.

[0] From Recital 23: "[When deciding whether processing is in scope under Article 3(2)], it should be ascertained whether it is apparent that the controller or processor envisages offering services to data subjects in one or more Member States in the Union."

I'd agree with that. Someone somewhere is probably going to complain about an instance where it failed, but I honestly would be surprised if regulators made a big deal out of it.

Re: getting your team more interested in testing. This is not an easy thing to get momentum on if people aren't used to it. Yes to getting the test time down (and keeping it down)

Also, try defining (maybe in collaboration with the team) the tests you want people to write rather than leaving it up to them or (hopefully not) expecting 100% coverage. I wrote this on my thoughts a while back https://getcorrello.com/blog/2015/11/20/how-much-automated-t... We had some success with increasing testing using that and code review so others could check tests were being written. Still not total buy in to be honest but a big move in the right direction :)

One surprising thing was that after years of thinking I was encouraging my team to write tests, the main feedback on why they didn't was that the didn't have time. Making it an explicit part of the process and importantly defining what tests didn't need to be maintained forever really helped.

I think it is reasonable to question what people mean by "can't discuss". As mentioned in the article people can discuss anything, but certain things are met with some pushback which makes discussing them hard or unpleasant.

I would say, if you hold one of these "taboo" opinions there is a reasonable amount of responsibility on you for how you open a discussion on them. If you do want to discuss them you need to try and raise them in a way which shows you are genuinely interested in discussion, including possibly changing your own opinion and trying to get a better understanding of others opinions without necessarily judging them. Rather than coming from a fixed position and trying to convert people, which in my experience rarely works.

If you hold one of more of these taboo opinions and think I am being rude, suggesting you don't discuss properly it that those you discuss with are all perfect reasonable beings that is not the case. But in my experience it is not common for people to open a discussion honestly looking to assess their own opinions as well as those they are discussing with. If you aren't open to change your mind, why should anyone be open to change theirs? If you are already doing that, then good for you! Hopefully some minds will get changed and we can all move forward with a more honest understanding of the world.

> If you aren't open to change your mind, why should anyone be open to change theirs?

A lot of discussion/debate is less about changing minds and more about mutual understanding of the underlying values. The problem is these "taboo subjects" all too often have people assuming the other's intentions and therefore the underlying reasoning for those bad arguments never get fleshed out. Thus the person with the taboo perspective just feels misunderstood.

I imagine this is also how athiests feel in deeply religious parts of the US.

Thanks for the big write up, very insightful.

I actually own my own business so focusing on things during work time isn't too hard (Always too much to do regardless of the hours I work). The need for some social contact is an interesting one as I we are also considering moving out of the town we live in with my family. I think we will use that as an excuse to join some local groups and get involved with things and hence meet people that way.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact