andreasklinger

Joined 16 years ago

Karma
3,127
Submissions
682
Member since
Jun 29
tech at www.angel.co & www.producthunt.com
View on Hacker News

Recent submissions

Comment · 3 years ago
https://klinger.io/

usually write stuff down that i keep repeating in discussions

- eg management advice: https://klinger.io/posts/managing-people-%F0%9F%A4%AF

- eg my angel-investment decision making process: https://klinger.io/posts/how-i-make-investment-decisions

- eg simple productivity-hack: https://klinger.io/posts/q-codes

Comment · 5 years ago
I think people here underestimate how much money will be made in climate tech in the next decades.

It's literally changing the map of the world, shifting the access (and use) of resources and the livelihood of people worldwide.

Not that i think it's a good thing that this needs to exist but mitigation and adaption to this change will be a huge industry.

Comment · 6 years ago
Quick tip:

Have a person that has call with the new intern every day for the first 1-2 weeks.

Blocked to be 30mins, meant to be 15mins.

It allows to "bring stupid questions / blockers" to the next day's meeting. It create bonding and team culture understanding.

Comment · 6 years ago
She was an amazing and inspiring person.
Comment · 6 years ago
I helped building producthunt.com and overclockers.at (and other less successful ones)

Here a few learnings:

1. the community already exists, you just create a communication platform for it

2. make it clear what the community is about [positioning/marketing]

3. make sure the communication/content is interesting [quality]

4. make sure there is enough engagement [perceived critical mass] (encourage people to post, post yourself a lot, fake accounts if needed, only create subforums once the main ones are noisy)

5. have a rhythm - some communities need daily good posts, some live of the weekly newsletter

Comment · 7 years ago
FYI: I would also add angel.co/jobs

AngelList has the largest amount of remote jobs right now out there

(Disclaimer: work at AngelList)

Comment · 7 years ago
Imho it matters less.

What's important is that you have rigorous testing around your API.

APIs are essentially external contracts people build against. You don't want to break this contract.

make sure it

- never changes unless you know about it

- updates the documentation whenever it changes

Comment · 7 years ago
blog author

you can use stars OR labels - no point using both

you have extra inboxes for each kind on the side

you read in your inbox you act (potentially reply, potentially mark with star/label, always archive)

if it's a todo you dont get to now you put it in the todo label if you replied and want to make sure you dont lose track -> awaiting reply if you handed it off to someone and want to keep track -> delegated if it's about some future meeting (or flight, hotel, etc) -> purple star (forgot what i called it)

you always archive this way your main inbox is empty and you know what you looked at by adding (or removing) label they end up (or get out) in the little boxes

at some point you might go through your todos - handle them remove the star/label

at some other point you might browse through the awaiting replies and realise they are done or no longer needed -> remove label

(and so on)

works really well for me

hth

Comment · 7 years ago
there were a lot of different tools when i wrote this post several other inbetween

main reason i never switched (even with all compromises) is that i didn't want to be forced to switch back if i pick the unlucky one (eg google inbox)

Comment · 7 years ago
i approach it the same way

or mark as "delegated" if someone else of my team is handling it and i might want to keep track

Comment · 7 years ago
:)
Comment · 7 years ago
disagree here but in favor of simplicity of the main message removed it.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton