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

Task Analytics | Fullstack engineer (JavaScript), Product designer / UX Engineer | New York / Norway | REMOTE, FULL TIME

Task Analytics delivers actionable, human insights that help create, shape and impact your customers online experience. Task Analytics captures and analyzes customer intent to establish and align strategies across any organization. The culmination of years of research in top task methodology and user testing, our platform is trusted by leading brands and digital agencies to deliver a non-invasive engagement tool that helps discover the why behind the metrics being measured by traditional web analytics tools.

We are a fully remote team but we also have office space in New York (US) and Oslo (Norway). We offer competitive salary and a highly flexible work arrangement tailored to fit your life.

You:

* Have intermediate (Designer) or expert (Engineer) JavaScript knowledge

* Know your field and have a habit of keeping up to date

* Personally think UX matters and can align with a users perspective

* Will work hands on on product in a tight knit team

* Have a track record of shipping

* Are self-motivated and a proactive team player

Some core parts of our stack includes: NodeJS, React & friends, ArangoDB.

Note that due to timezone overlap constraints we can only hire in Eastern USA and Europe at this stage.

Please read actual job postings for more information:

- https://weworkremotely.com/remote-jobs/task-analytics-full-s...

- https://weworkremotely.com/remote-jobs/task-analytics-produc...

You can apply at https://weworkremotely.com/company/task-analytics or email [email protected]


I would be happy to contribute $ towards an improved Z-Wave implementation in HA if its based on an official SDK. I'm pretty sure I know a few others who would do the same if you set up a funding campaign somewhere.


Task Analytics | Software Engineer | EUROPE | ONSITE, REMOTE https://taskanalytics.com

We are a small Norwegian startup helping our customers understand their users by building the next evolution in digital analytics. We are currently 10 people spread over Norway, USA and Sri Lanka. We will tailor the position to your skillset and desires.

MUST be

- Self-motivated

- Communicate well (remote work can be hard)

- Passionate about programming

- Quality focussed

Possible requirements

- Strong Javascript, Node.js and/or React experience

- Experience building data pipelines

- Knowledge of Mesos, DC/OS and Marathon

- ArangoDB experience

- DevOps

Perks

- 6 weeks paid vacation (no as-much-as-you-want fake vac.)

- Conference budget

- Annual company retreat

- Great colleagues

- Learning environment

Apply at https://taskanalytics.com/careers/software-engineer/ or reach out @nervetattoo anywhere


I was dissapointed to find that this site was not about resources for "making", as in Maker Movement. I was expecting a good library of things like "How to make an armchair", "How to build your own 3d printer".



Not free, but the most recent Humble Books Bundle has a bunch of stuff targeted to the Maker crowd:

https://www.humblebundle.com/books


Yes, the term maker is quiet broad these days. There's no reason I can't expand it to the different types of makers I guess. Thanks for the feedback.


In 2009 how was the term used by pg?

http://www.paulgraham.com/makersschedule.html


After nailing your base jump pitch you'll kill it at elevator pitches!


There should be some personality traits overlap between extreme sports people and people creating startups, so combining the two seems interesting.

High intensity events tend to bring people together quicker, so this could potentially create some unique connections between potential founders.

Also, being Norwegian its nice to see Norways strengths being used!


You couldn't run tests only on your staged changes pre-commit without the staging area. Right now my pre-commit hook stashes any non-staged changes, from inside the same files that has staged content, and then runs tests. This ensures I can create commits with just the stuff that works of my changes without first removing the ongoing work.

The staging area surely adds complexity, but if you do not like it then simply don't use git.


> This ensures I can create commits with just the stuff that works of my changes without first removing the ongoing work.

If I have ongoing work I want to remove, I just stash it, as you said. I don't need a staging area to stash things, and it's pretty rare that I'll have unrelated work anyway.

> The staging area surely adds complexity, but if you do not like it then simply don't use git.

Ah, the old "your arm hurts? Just cut it off!" solution. Yes, I will just not use git, I will just email my team diffs.


Actually you need to stop earlier, I've found that quite a bit of the stuff that people think they need to have built isn't even close to needed in reality. In fact, building it and shipping it can be a major mistake itself.

So I completely agree on the underlying principle: Dont to _anything_ prematurely, and that first and foremost includes actually writing any code at all.


Actually you need to stop earlier, I've found that quite a bit of the stuff that people think they need to have built isn't even close to needed in reality. In fact, building it and shipping it can be a major mistake itself.

So I completely agree on the underlying principle: Dont to _anything_ prematurely, and that first and foremost includes actually writing any code at all.


Boy, if you take this a bit too seriously, you're going to end up putting yourself out of a job.

I could write this new product... but the market is already saturated with products that kind of already do this... they probably don't need mine.

The exception to that opinion is social networks. If you think you need to build a new social network, stop yourself and erase any traces of that thought from your mind.


Same with writing a blog post, and commenting it here. We're going Buddhist.


I've complained a few times on twitter to @github about removing the traffic graph. I used it as a motivator myself, and a way of trying to prioritise what project to work on.

A spike in traffic could mean I invested that extra time to land something new in a project, that was a great way for github to ensure commitment in projects.

Apart from that I think every change in the last six months have been good.


Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

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

Search: