Hacker Newsnew | past | comments | ask | show | jobs | submit | daemonl's commentslogin

ECAL | Melbourne, Australia | ONSITE

Join our small, high performing team as we split our monolith to micro-services.

- Backend developer: familiar with complied languages and database constraints. https://www.seek.com.au/job/37123997

- Frontend developer: we like React/Redux, but it would be your stack to own.

Apply to damien@ecal.com

ECAL is a calendar management company, we allow clients such as the English Premier League, Ticketek and MLS to publish calendars into subscriber's calendars via ICS, and Google and Microsoft APIs.

Current stack: PHP (zend-ish), Mongo, EC2

New stack: Docker, ECS, then the 'best tool for the job', so far we have added Go for network heavy things, Python for Spark and Ops, a little Node, Postgres for the data, React on the front.

I'm hiring for people I can trust, who can take an idea and make it work whilst collaborating with the team on micro-service contract design, testing, and 'best practices' within each service. Strong opinions, loosely held etc.

These are not entry-level positions, but we aren't looking for 'ninjas' either. We are more interested in what you can do with us than what you have done in the past.

We are looking for the best candidate for the position, you will be considered based on your skill and passion for programming, not your race, religion, gender, age, sexuality, political leanings, eye colour, opinions on cubism or the oxford comma, or anything else not related to programming.


ECAL | Backend & Frontend Devs | Melbourne, Australia | ONSITE | https://ecal.com/

Join our small, high performing team as we split our monolith to micro-services.

- Backend developer: familiar with complied languages and database constraints.

- Frontend developer: we like React/Redux, but it would be your stack to own. https://www.seek.com.au/job/36803616

Apply to damien@ecal.com

ECAL is a calendar management company, we allow clients such as the English Premier League, Ticketek and MLS to publish calendars into subscriber's calendars via ICS, and Google and Microsoft APIs.

Current stack: PHP (zend-ish), Mongo, EC2

New stack: Docker, ECS, then the 'best tool for the job', so far we have added Go for network heavy things, Python for Spark and Ops, a little Node, Postgres for the data, React on the front.

I'm hiring for people I can trust, who can take an idea and make it work whilst collaborating with the team on micro-service contract design, testing, and 'best practices' within each service. Strong opinions, loosely held etc.

These are not entry-level positions, but we aren't looking for 'ninjas' either. We are more interested in what you can do with us than what you have done in the past.

We are looking for the best candidate for the position, you will be considered based on your skill and passion for programming, not your race, religion, gender, age, sexuality, political leanings, eye colour, opinions on cubism or the oxford comma, or anything else not related to programming.


"When wellbeing is at stake, truth should be the principal concern. "

"a critical mindset ... is our only hope in a world so full of bullshit."

I agree wholeheartedly... but I have no proof or reason to back it up - why is it so important?


I love the way you have expressed this, kind of what I'm trying to get across to people but can't quite put it into words.

Any interest in fleshing it out into a whole post?


I use the introduction text from the Wikipedia article on lorem ipsum. Best of both worlds, and meta lols.


Wow, that's perfect!


Yep. As is google search - a little bit, anyway


That's really detailed feedback, thanks for that!

I'm actually fighting with some interesting things now with error handling, I wan't aware I had to do my own retry on deadlocks.

Ugh, it's just one of those days I feel like I'm not as good at this as I thought I was.


If you know where the deadlocks are likely to occur, consider turning to a sync.Mutex and wrapping the statement in a lock. It will cause other goroutines to wait until the lock is free.

It all depends where the deadlocks are though, you can easily achieve them in the Go code as well as the database queries.

I'm not around much today as I'm with a client this morning and lunch, but if you're stuck later I may well be in https://gophers.slack.com/ . Happy to help out if I can, as I'm sure most others will be.


Or... lack of project management.

There is definitely something to be written on that, but - well I'm not the guy. Yet.


We could start one?

I think that's what HN kind of is...


Yep. I know. I even deleted the github repo. I'm seriously not sure what I was doing. Remove all traces of a bad idea?


Ouch, why on earth...

Anyway, good blog post.


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

Search: