pixelrevision

Joined 8 years ago

Karma
537
Submissions
225
Member since
Dec 31
View on Hacker News

Recent submissions

Comment · 2 years ago
And unfortunately “productive” needs to be part of the package. I have worked with some incredibly smart people that I really respected who had a very hard time getting anything done.
Comment · 2 years ago
You can earn cash shop points by doing a lot of grinding.
Comment · 3 years ago
Thanks, I really didn’t get what they meant with the example they were using.

Out of curiosity why is writing everything as a single element type more ergonomic? I’ve not done frontend web dev in a while and using <p> <h1> and so on seems like it would be more ergonomic to express intent.

Comment · 3 years ago
Heh. Going to be a lot less maintenance work if they are.
Comment · 3 years ago
At work we use snapshot tests to see visual changes to ui. It helps a lot with code review especially with adding edge case data to tight designs.

We use ui tests specifically for testing accessibility, analytics and data passed along during navigation.

We use fixtures for all of this.

None of these tests really help with bugs. What they do help with is:

- Making sure the ui stays really decoupled from the business logic. This helps a lot with getting the data unit tested which does help a lot with bugs.

- Making sure that analytics and accessibility are not forgotten about. This helps a ton when refactoring.

- Making the intent of the code really clear during review.

It takes a bit of practice and being ruthless about removing/fixing stuff that’s not helping. I have found it makes it much easier for new developers to work, review code and understand how the code is organized. YMMV.

Comment · 3 years ago
Spoiler: no one thinks they should have to pay for software these days.
Comment · 3 years ago
It really has caused a race to the bottom anywhere it becomes the primary business model. Everyone hates it but no one’s got a solve to get people paying for things once they are “free”.
Comment · 3 years ago
Unity is a really good alternative. Flash kinda went sideways and started really trying to lean into the Java crowd with flex. Unity is more like what would have happened if Flash heavily leaned into what it did well.
Comment · 3 years ago
Yes. And the tooling is pretty straightforward to plug into generally if you need to tweak things. I’ve found that the biggest barrier here is generally not in openapi tooling, but in getting people to take time out to leverage it. This is one of those places that having lots of options and alternatives typically makes things worse.
Comment · 3 years ago
“I don’t have to finish this” is also quite liberating
Comment · 3 years ago
It also doubles as documentation that’s forced to stay up to date. Code has a way of becoming hard to follow especially when edge cases and performance enhancements are added.
Comment · 3 years ago
Adding software can help.

Alfred can either replace spotlite or run along side it. I’ve found it much faster and easier to use. You can customize it pretty well. (Just don’t download the Mac App Store version as it’s multiple versions behind)

There’s a ton of windows managers out there that help you setup hot keys or modify windows to work how you want. Mac overall is much better with native software not doing its own thing than windows so changes tend to be pretty consistent. I’m using MOOM because it’s on the app store and lets me hotkey all my windows into specific sizes but there’s plenty of other stuff out there depending on what you want to do.

Comment · 3 years ago
I think the problem here is that there are very few places where there is any time between pressing feature demands. This always seemed to me what the agile guys were saying. The approach was all centered around the idea that things would always be changing and pressing. The only way to combat that is to put constant refactoring into the day to day so that your codebase can remain coherent and productive to work on.

The bonus of doing things like this is that if you are constantly changing your code then it becomes battle hardened to accept change. This gives you better ability to keep up with the changing demands of both customers and technology.

Comment · 3 years ago
Comment · 3 years ago
Some of the best engineers I’ve ever worked were just “going with the flow”. They certainly brought tons to the table. Some people are just quiet and don’t like conflict. If you ask them what they think plus give them a calm environment, time and support you can find yourself looking at some very elegant easy to maintain systems.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton