Recent submissions

Comment · 1 year ago
Location: Bielefeld, Germany

Remote: Yes

Willing to relocate: No

Technologies: Typescript, Python, LLMs, Node, React, NestJS, Redis, Postgres, ...

Résumé/CV: https://www.linkedin.com/in/pdyck/

Email: dev dot pdyck at gmail dot com

Senior engineer with 10 YoE. Broad domain expertise in customer service, project management, martech, adtech and legal tech building B2B SaaS and AI-powered products. Looking for part-time freelance gigs.

Comment · 3 years ago
Location: Bielefeld, Germany

Remote: remote preferred

Willing to relocate: no but occasional travel is fine

Technologies: Node.js, React.js, TypeScript, Java, Spring, SQL, AWS, Docker

CV: https://www.linkedin.com/in/pdyck

Email: {HN username}@posteo.de

Full-stack/product engineer with 8 years of startup and enterprise experience. Would love to join a company that makes complicated things easy. :)

Comment · 3 years ago
Location: Bielefeld, Germany

Remote: remote preferred

Willing to relocate: no but occasional travel is fine

Technologies: Node.js, React.js, TypeScript, Java, Spring, SQL, AWS, Docker

CV: https://www.linkedin.com/in/pdyck

Email: {HN username}@posteo.de

Full-stack/product engineer with 8 years of startup and enterprise experience. Would love to join a company that makes complicated things easy. :)

Comment · 5 years ago
Valuedesk (https://valuedesk.de) | Bielefeld, Germany (ONSITE) | Full-time | Senior Software Engineer

At Valuedesk we help industrial companies to introduce a sustainable and plannable process for cost optimization. We are building a product that enables our customers to turn their employees’ ideas into real savings by supporting them at every step of this journey.

We are looking for a Senior Software Engineer to join our product engineering team. You will be working alongside a product manager, a designer and other engineers to ship features from end-to-end while improving our processes and infrastructure.

Are you interested? Send us a short introduction or your LinkedIn profile to [email protected]

https://valuedesk.jobs.personio.de/job/399391

Comment · 5 years ago
Valuedesk (https://valuedesk.de) | Bielefeld, Germany (ONSITE) | Full-time | Software Engineers

At Valuedesk we help industrial companies to introduce a sustainable and plannable process for cost optimization. We are building a product that enables our customers to turn their employees’ ideas into real savings by supporting them at every step of this journey.

We are looking for a Senior Software Engineer and multiple Software Engineers to join our product engineering team. You will be working alongside a product manager, a designer and other engineers to ship features from end-to-end while improving our processes and infrastructure.

Are you interested? Send us a short introduction or your LinkedIn profile to [email protected]

https://valuedesk.jobs.personio.de/job/326875

https://valuedesk.jobs.personio.de/job/326874

Comment · 5 years ago
Comment · 5 years ago
The biggest improvement we made to our dailies was to break up the traditional three question structure. Nobody really cares about your status from yesterday. Especially since we work together every day and are a self-organizing team that does not need to report to a manager on a daily basis.

Instead we talk about our plans for the day, ask a lot of questions and plan our collaboration and problem solving sessions. These dailies are usually shorter and I feel like I get much more value from them.

Comment · 5 years ago
Comment · 5 years ago
Comment · 5 years ago
Comment · 6 years ago
Comment · 6 years ago
Services like S3 are referred to as „object storage“. AWS Lambda is a service for „serverless compute“ or „function as a service“ (although it‘s debatable if these are good names for the concept).

My point is that definitely are named for these concepts but AWS uses brand names which is quite confusing for people who are new to AWS.

Comment · 6 years ago
Why is this better than throwing errors or using Promise.resolve()?

I know it is inefficient because creating a new error with a stack trace each time is bad for performance. However, you can also throw errors which do not extend Error to avoid this. Destructuring the output and explicitly checking for errors every time seems to be quite the hassle.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton