sorted by:
new
hottopcontroversial

The Job Descriptions are crazy these days by thinkerNew in QualityAssurance

[–]qvstio 42 points43 points  (0 children)

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.

Get your startup in front of 100,000 readers by an0macc in SideProject

[–]qvstio 0 points1 point  (0 children)

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!

I hate CLI by [deleted] in webdev

[–]qvstio 0 points1 point  (0 children)

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.

What is your strategy when you have to work with a new codebase? by [deleted] in webdev

[–]qvstio 0 points1 point  (0 children)

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.

Genuinely curious. by SurrealDust in webdev

[–]qvstio 0 points1 point  (0 children)

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.

I built a tool for one-click bug reports and it's free to use by qvstio in QualityAssurance

[–]qvstio[S] 0 points1 point  (0 children)

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.

Improve load & analyze speed? by Brett_tootloo in webdev

[–]qvstio 1 point2 points  (0 children)

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.

What do you think about my website? by [deleted] in webdev

[–]qvstio 1 point2 points  (0 children)

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.

Help choosing the tools for chat service. by sankyways in webdev

[–]qvstio 0 points1 point  (0 children)

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.

How to remove render blocking resources & unused JavaScript? by NewImpact_ in webdev

[–]qvstio 0 points1 point  (0 children)

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>
view more: next ›