desc

5 ms·

1.
by desc 4y ago
Apropos of nothing, and anecdotally: 2 years seems to be about the length of time it takes for a solution to become the next problem.
2.
by desc 5y ago
It depends how you count the unit/integration tests, really. If you've got a general rule which must apply across an entire system, generate the necessary tests so that they fail granularly and don't require messing around to
3.
by desc 5y ago
Silver bullets. They don't exist. Code review. Read the results of someone thinking through a process. Spot more than they will, simply by throwing more eyes at it. Actually fairly effective: getting a senior dev to cast even a lazy
4.
by desc 6y ago
This. Jira is a framework for building something which approximates your actual processes. > Justin said “I wish Atlassian would sit down with real-world developers and design this product the way we need it to work.” The way 'you&#
5.
by desc 6y ago
Some other commenters have mentioned environment variables as input. IMO there are broadly two types of command: plumbing and porcelain. There's a certain amount of convention and culture in distinguishing them and I'm not going t
6.
by desc 6y ago
I meant that 'creating' is rather the wrong tense, and that this is probably a symptom that it's pretty well entrenched by now.
7.
by desc 6y ago
88. If the signaling value of a college degree is its most valuable part, then we are creating a society that values the appearance of success more than actual success. Someone might be a bit confused about where the causality arrow is poin
8.
by desc 6y ago
I prefer to internalise useful ways of thinking rather than leaning too much on tools, on the grounds that the latter are easy-come-easy-go while the former can last a lifetime. Learn to explain what you're building, why, and more-or-l
9.
by desc 6y ago
This, most of all. Substitute native language if not English; the important thing is that the project be defined and developed in both a human language and a computer language, so that mismatches can be identified and resolved. * Star
10.
by desc 6y ago
You mean like the OS is supposed to be?
11.
by desc 6y ago
1. Our customers run our software on their own machines for security and data-control reasons. As soon as something's running on someone else's hardware, the data is out of your control. Unless you're going to accept the (oft
12.
by desc 6y ago
https://stackoverflow.com/questions/898489/what-programming-... Most languages have context-free syntax, which is what the article refers too. There really is no reason to sacrifice that. Even modern PHP recognise
13.
by desc 6y ago
Hmm, so the reusable bit is the straightforward inject-everything component, driven by an app-specific, app-aware hook-using part? I can see how that can work for simple cases. Nesting components is going to get tricky though if the classes
14.
by desc 6y ago
I'm going to express something a lot of people are thinking and are being far too diplomatic about. React Hooks are a fucking stupid idea and always were. They're basically just adding dynamic scoping to a language and framework
15.
by desc 6y ago
Bad shit happens to a minority of people every day, permanently disrupting their lives and forcing them to abandon long-term plans. The majority remain oblivious and see an enduring status quo. Suddenly a Black Swan craps on everyone at onc
16.
by desc 7y ago
Then you charge a reasonable price. You don't put a 'free' sticker on it with an unknowable 'ad revenue' cost in the background. One might argue that the customer should know the price they pay in advertising data-s
17.
by desc 7y ago
"People don't consider my games worth what I spent to make them, so I'll sneak in adverts too so I don't have to charge them more and pop their little bubble, so they can continue thinking games are this cheap because th
18.
by desc 7y ago
Indeed, and this was measured, and the improvement was worth it. Profiling! :P The cost isn't always where we think it is. Still, 'turn off exceptions because exceptions are slow' is a daft rule of thumb for the majority of s
19.
by desc 7y ago
sigh If your application is slow, odds are it's not because you used exceptions. If you're throwing enough exceptions for this to matter it'll show up on a profiler, and then you can change that specific chunk of code to av
20.
by desc 7y ago
Because we wouldn't want mere icons distracting the user from being distracted by all the other stupid animations in the average UI.
21.
by desc 7y ago
The 'someone' in question probably wasn't the engineer. I'd bet the engineer was listening to the 'someone' saying things like 'why don't you just' or 'it just needs to do this', or oth
22.
by desc 7y ago
This could be done, if everyone involved were willing to accept massive risk to the lives of the astronauts (including the astronauts, obviously). By which I mean, after hurriedly building rockets and testing them, finally going ahead with
23.
by desc 7y ago
I know why this happens. It happens because someone doesn't understand that search rankings vs. queries have to have a 'smooth' solution, and thinks they can tweak a few weightings here and there to get the results they think
24.
by desc 7y ago
Can't say I ran into this particular bug, but I tend not to trust the search on Windows much anyway. I myself have implemented better text/prefix matching and ranking using a very simple SQLite database schema, on a far larger d
25.
by desc 7y ago
The problem is that this is a bunch of bollocks. But at the same time, that might actually resolve my problem with it as the pain gets fed back. If one is very very lucky , a library will have accurate changenotes explaining what the versi
26.
by desc 7y ago
And all the new bugs introduced in the process.
27.
by desc 7y ago
Yes, that's why these cost me a few weekends... if it's done in my Free Time(TM) they don't have to know about the unsuccessful ones.
28.
by desc 7y ago
I agree with this. One of the best changes we ever made was embracing a branch-heavy merge-centric workflow for literally everything . There was considerable pushback initially because it was perceived as 'complicated' but that d
29.
by desc 7y ago
This. When something needs doing, I just get it done. If you wait for everyone to agree that it needs planning to be done at some point in the future, it'll never get done because the feature firehose never relents. This has cost me a
30.
by desc 7y ago
I actually invested some time a while back in building a nicer API for C# to invoke shell commands and process the results. The only downside IMO is the Rx library dependency for STDOUT/STDERR; I personally try to avoid depending on li

More ›