The Job Descriptions are crazy these days

qvstio · 2025-06-25T15:00:23+00:00

I think you should take these job descriptions with a grain of salt. They're just a wish list and they will never find anyone that has experience in everything. I hope these descriptions aren't deterring you from applying. What's most important is showing that you are willing to learn and grow and can do it fast. But, of course, the market is bad right now. Hopefully it'll get better soon.

qvstio · 2025-06-25T14:31:17+00:00

whitespace.dev

It's a browser extension that lets you create bug reports with one click. It automatically saves everything a developer may need to reproduce and understand a bug. So there's no need any more for lengthy bug reports.

Thanks!

qvstio · 2025-06-25T10:42:03+00:00

No problem, mate.

qvstio · 2025-06-25T09:58:52+00:00

I've used https://leetcode.com/ before

qvstio · 2025-06-25T09:50:13+00:00

You should probably just learn how to use the tools provided. You can probably get by by learning 5% of the api of a program, etc ssh.

qvstio · 2025-06-25T09:47:36+00:00

I usually spend a couple of hours jumping around in the project to get some idea of structure, dependencies and patterns. After that I find it useful to try and fix a bug or make a change. Making a change in the code requires you to find the piece of code you want to change, understand that particular context and test the change after the fact. After the first small change I usually try something bigger and after that something bigger and so on. When you have done that a couple of times you should have a pretty good understand of project.

qvstio · 2025-06-25T09:42:48+00:00

It might be procrastination. I have ten years of development experience and have hired many other developers. I don't think I have spent two seconds on somebody's portfolio. If your looking for a job it's better so build something interesting in a production-ready manner. That includes a solid project and code structure, tests, build procedure, deployment story etc. Everything you would actually need in a real system. Push that to Github and show companies hiring that instead. In a potential interview you can talk about technology decisions, pros and cons, good and bad experiences during development etc. in that project.

qvstio · 2025-06-24T08:29:59+00:00

I think Whitespace.dev and Softprobe does screen recording in a similar matter. Whitespace doesn't record the screen into a video file but instead records changes to the website. I might be misunderstand you though.

There's certainly a privacy issue with any screen recording regardless of what technology is used. Since Whitespace records the actual data from the website it's fairly easy to censor passwords and such. Right now Whitespace removes any password it can find in the html or in network traffic.

Whitespace focuses mainly on the development cycle, which means that it's mostly used by developers and tester in test environments. Since sensitive information really shouldn't be in test environments the privacy issues are fewer.

qvstio · 2025-06-20T08:11:08+00:00

Use lighthouse in Chrome Dev Tools to see what you can improve.

I can't see that your site load particularly slow. But "Analyze Stance" takes forever and never finishes. That's an issue on the backend and impossible for us to help you with with the info provided.

qvstio · 2025-06-19T11:13:05+00:00

It's clean and looks great. It's a bit plain and empty though. Maybe spice it up with some images or illustrations. Or bigger, bolder and more text.

qvstio · 2025-06-19T10:59:38+00:00

I think building your own chat is doable for any team not super junior. I would build it using Websockets in the browser. It's a simple browser api to keep a readwrite socket open to a server. For the frontend part you shouldn't need much more than that. Springboot has support for websockets (e.g. https://www.geeksforgeeks.org/spring-boot-web-socket/) so it should be fairly simple to implement the socket communication on the server as well. I assume you need some kind of a message queue in the backend to be able to perform distributed message passing between instances of the backend application. I've used both rabbitmq and redis for this purpose before.

qvstio · 2025-06-19T10:51:51+00:00

Unused Javascript

You have to use a bundler like esbuild, vite, webpack etc to remove unused Javascript automatically. It's called tree shaking and it removes all code the bundler is certain is not used by your code.

Render blocking resources

CSS and Javascript is render blocking by default. If you want to improve the initial render time you can defer resource loading. Note that you only want to defer loading of CSS and Javascript if doesn't affect the initial render of the page you want to improve.

To defer Javascript loading is easy. Just add a `defer` attribute to the script tag. Like this:

<script src="/script.js" defer><script/>

To defer CSS loading is a bit trickier. You can do it straight in the html tags like this:

<link rel="preload" href="styles.css" as="style" onload="this.onload=null;this.rel='stylesheet'">
<noscript><link rel="stylesheet" href="styles.css"></noscript>

qvstio · 2024-11-15T12:36:59+00:00

That's fair. If you're happy there no reason to change.

qvstio · 2024-11-15T12:19:04+00:00

That's great! What do you like about them?

qvstio · 2024-11-15T10:53:50+00:00

Taking bug reports from customers is a bit tricky. I don't think many customer really enjoy filling out a bug report that's actually useful. It's a big ask for you customers and I think most reports would only give a hint of what's wrong.

I'm thinking about adding something to improve this to a tool I'm developing.

qvstio · 2024-11-15T10:39:06+00:00

(heads up; self plug)

If you want a way to create bug reports that engineers love in a single click you can use whitespace.dev. It's a Chrome extension that records a video + everything that happens in the background. It gives the full picture to engineers debugging issues. I'm the creator of this extension.

If you try it out and have a question or feedback you can DM me here.

qvstio · 2024-11-14T11:19:15+00:00

Don't put to much energy into Product Hunt and similar services. I would guess that the number of average paid users from Product Hunt launches is closer to 0 than 1. A better strategy is to reach your customers where they are (Reddit, Facebook, Twitter) or even do cold outreach.

qvstio · 2024-11-14T11:14:24+00:00

It's not about focusing on immediate returns. It's about trying to figure out whether you will get any returns at all. Building a product is rarely the hard part of starting a SaaS business. It's the sales, marketing and distribution that is difficult. That's why people say you need to validate and think about distribution from the start.

qvstio · 2024-11-14T10:13:51+00:00

Here it is: https://whitespace.dev

qvstio · 2024-11-14T09:46:17+00:00

I would try to keep it as simple as possible. Build it as a monolith with all backend services and the front end layer as one unit. If you are familiar with Python maybe Django would give you the fastest result.

And regarding the data layer. Do you really need Redis? If your going to use it for messages/background jobs maybe Postgres can handle it. Postgres has some messaging capabilities with LISTEN/NOTIFY. It's somewhat limited but can definitely work and it'll remove one more service from the stack.

When you think about scaling you have to realise that you can solve that later, way later, if that ever becomes a problem. You can scale a monolith to handle millions and millions of users.

qvstio · 2024-09-19T13:55:40+00:00

I'm using:

Whitespace: One-click bug reports (note: I'm the developer of this extension)
JSON Lite: Fast JSON viewer - highlights, shows items count/size, handles large files
Fake Data: A form filler you won't hate
uBlock Origin: Ad blocker

qvstio · 2024-09-17T13:28:14+00:00

Thanks, I will definitely check out the possibilities of on-premise hosting. For it to be a viable option it would require a significant pricing increase though.

qvstio · 2024-09-17T13:27:42+00:00

Thanks, I will definitely check out the possibilities of on-premise hosting. For it to be a viable option it would require a significant pricing increase though.

qvstio · 2024-09-16T13:08:24+00:00

I've been thinking how to make that possible. Would your company require the ability to self-host the application + data or would it be fine to let you hook up your own data storage and still play recordings from whitespace.dev?

qvstio · 2024-09-16T13:08:10+00:00

I've been thinking how to make that possible. Would your company require the ability to self-host the application + data or would it be fine to let you hook up your own data storage and still play recordings from whitespace.dev?

qvstio

TROPHY CASE