jpswade

12 ms·

91.
by jpswade 5y ago
It seems obvious to me that the decision to remove ports and buttons is not only for the design aesthetic, but less moving parts means less problems, less weight, less insulation, less cost and more elegant wireless peripherals to sell. If
92.
by jpswade 5y ago
There's a school of thought in interface design that you shouldn't change what the user inputs, as it can be a jarring experience for regular users.
93.
by jpswade 5y ago
The code should explain what it's doing (self documenting code) and tests should explain why it's doing it. Comments tend to just become a place for misinformation or get disconnected from the actual logic. Adding more comments so
94.
by jpswade 5y ago
Burnout is something that is discussed quite a lot, but people talk about it as working so hard that you fatigue. When we're working on something we enjoy and find interesting, when we have a plan and a goal, we find that we have infin
95.
by jpswade 5y ago
No, it predicted Dropbox would be dead.
96.
by jpswade 5y ago
Technical debt implies that it is a technical decision, when mostly it’s a business one. Debt has a negative connotation, where as it’s more like a mortgage. I always wonder if there’s an equivalent term in manufacturing.
97.
by jpswade 5y ago
Alternativeto.net
98.
by jpswade 5y ago
I had a look into this as part of a research project. To reduce the burden of writing specific scraping software, I investigated the software listed by the Archive Team[0]. The command line tools and libraries aside (as they would require m
99.
by jpswade 5y ago
I rarely think tech debt is actually technical debt, that would imply it’s totally down to a technical decision when most of the time we make technical decisions based on real business requirements that were appropriate at that time. For ex
100.
by jpswade 5y ago
So you have a DevOps team? Who is doing what wrong, according to whom?
101.
by jpswade 5y ago
The DevOps tool chain has become so complex that it requires specialist roles that create knowledge silos. The goal of DevOps was to remove those gates and silos. It was meant to be about skills over roles. All we appear to have done is cha
102.
by jpswade 5y ago
Here we go again. The view in this article is that DevOps is a role, it was never meant to be this way. The whole purpose of DevOps was to break down barriers between Dev and Ops, by not creating specialist roles and allowing developers to
103.
by jpswade 5y ago
Pretty sure copyright and IP laws don’t overrule innovation.
104.
by jpswade 5y ago
Not only this but a huge amount of publicly available code is truly terrible and should never really be used other than a point of reference, guidance.
105.
by jpswade 5y ago
There’s two problems, naming is hard and people think it doesn’t matter, that it’s just semantics or bike shedding when actually it’s probably one of the most important things. Naming things correctly is as important as well written code it
106.
by jpswade 5y ago
Join a club or group.
107.
by jpswade 5y ago
This feels like over-engineering a problem at it's finest. Taking 3 lines of ubiquitous code and abstracting in a new way, when it already does what you need out of the box. The base url and header details such as api token can all be
108.
by jpswade 5y ago
Tests should really fill this gap, not comments.
109.
by jpswade 5y ago
Back before computer systems, computers were people who did calculations. It’s maths at its core. Computers today are surely then just applied computer science.
110.
by jpswade 5y ago
I used to love UltraEdit, it would open huge binary files easily. The only downside was the price.
111.
by jpswade 5y ago
Do I miss IRC drama? No I don’t think so.
112.
by jpswade 5y ago
This is fantastic news.
113.
by jpswade 5y ago
Todos are generally terrible practice in code, as they often don’t give any indication how they are going to get to done. They never get prioritised and very rarely does anyone get to do them. So what’s the point? It feels like a todo is re
114.
by jpswade 5y ago
It’s a good question, but if you care about the audit trail, then perhaps event sourcing is a better choice. So yes, this only assumes you care about when the on state happened and you don’t care about the history.
115.
by jpswade 5y ago
I've yet to find a case where using a timestamp over a boolean hasn't been the better option. This is because turning a boolean on is an event so it'll always have a timestamp. Sometimes it's useful to know when this eve
116.
by jpswade 6y ago
This can’t really happen otherwise there will be no children to ask the question.
117.
by jpswade 6y ago
Walk the board is always better because it focuses the mind on what’s important.
118.
by jpswade 6y ago
https://m.soundcloud.com/hm2k
119.
by jpswade 6y ago
I’ve actually been investigating cPanel alternatives as it’s become expensive and I think customers should have choice. I find it interesting that I didn’t come across this one in all of my research I did last week or so, even though it’s b
120.
by jpswade 6y ago
Isn’t it mostly just glue?

More ›