lugg

22 ms·

241.
by lugg 7y ago
I find it strange we the people for the people by the people don't just straight up outlaw things like this with an amendment. The constitution is a great document that lasted far longer than expected. And surprisingly holds up extreme
242.
by lugg 7y ago
Why cringe? Hype creates burnout. The churn is absolutely untenable in the UI space right now and hasn't shown signs of slowing down anytime soon. Where I work we have 3-4 different ways of accessing our monolithic backend, and on top
243.
by lugg 7y ago
Survivorship bias. I'd also posit that there isn't much competition at the top.
244.
by lugg 7y ago
> Your tests are probing your code on a narrow range of inputs drawn from the valid state space that is almost always too large to actually verify. You don't need to verify all inputs with mathematical certainty. You're writing
245.
by lugg 7y ago
You've repeated AP's failing this isn't a workflow nor a replacement replacement debugging concept. It is a design paradigm that lessens the need for heavy weight debugging. Debugging still has its usecases. I, like others, j
246.
by lugg 7y ago
No. You're misrepresentating or misunderstanding the claim. It is not about debugging. It is about program design. If you need to step through execution in order to understand and reason about iit then your design is too complex. It is
247.
by lugg 7y ago
https://reddit.com/r/financialindependence
248.
by lugg 7y ago
If that's the real problem this is the wrong solution. I don't care how good your hiring practices are, there is zero chance you get 5000 devs using this stack correctly. Less is more at this scale.
249.
by lugg 7y ago
You're still blocked from using later features potentially even reaching a dependency chain deadlock until you update. Systems like this work far better when you just work to not break backwards compatibility full stop. Similarly, they
250.
by lugg 7y ago
Monolithic just means it can carry out all it's required functionality alone, i.e. it's [major] dependencies are internalized. It doesn't say anything about not being able to be broken into modularized sections, services, or
251.
by lugg 7y ago
Agreed, microservices is literally a last resort in my book. It's the thing you reach for when you're hiring a new team worth of developers every other week and can't avoid developer blockage any other way. It's not even
252.
by lugg 7y ago
Code formatting, code style, and linting is a solved problem. If you're relying on individual developers to setup their Dev Env to do this you're doing it wrong. You need to have it automated with commit hooks. Anything else is a
253.
by lugg 7y ago
Agreed, I think too many people assume their code will live in their small team forever and ever. When you have a few thousand people committing daily it's a different story you need to keep consistency high and the jumping between pas
254.
by lugg 7y ago
... The answer to "why?" goes in the tests. Use commits for an audit trail of ticket numbers, urls, and playing the blame game. Use comments for expressing the inferred. // That which is not explicitly stated.
255.
by lugg 7y ago
Who? People that type with two fingers and can't tell the difference between Safari and google. You live in a bubble my friend. I've seen it in the wild and it's a marvel to watch how much they use it.
256.
by lugg 7y ago
Mostly agree. Might want to rethink the nitpick thing. > The goal is not to deliver perfect code. That's impossible - we're human. Trying to do so anyways is counterproductive. If it's not important why are you saying anyt
257.
by lugg 7y ago
Hah! I get the reference. What do I win? https://youtu.be/rcKxS2rbEdg
258.
by lugg 7y ago
Reminds me of the old you are not done yet list. Couldn't track the one I'm thinking of down but found this: http://www.thebraidytester.com/downloads/YouAreNotDoneYet.pd... I feel like I could use a checklist
259.
by lugg 7y ago
This assumes a BA is cheaper and more available than a programmer. If they are cheaper, I guarantee you're going to have problems. You're literally installing a weak link in the most crucial part of the chain.
260.
by lugg 7y ago
Something something history something something repeat it.
261.
by lugg 7y ago
All of those things are what a developer worth anything to a company should be doing. Similarly, BAs without business domain knowledge are even more worthless because of this. I.e. consultant BAs are, as most of us know, a waste of money. B
262.
by lugg 7y ago
Im surprised you missed it. Businesses solve this problem by hiring and training programmers in their business model and domain. Coders, are worthless. Coders with business acumen and domain knowledge are invaluable. This is also why I will
263.
by lugg 7y ago
> Because Amazon has chosen to allow that, for reasons which probably have to do with money. Yea.. that, nor the tirade that follows comes close to answering my question. I also suspect your thinking and reasoning are incredibly misguide
264.
by lugg 7y ago
Why would a product change even be allowed they're different products. Manufacturers don't get to claim this year's junk is so much better than last year's junk that I just have to buy it all the while claiming it's
265.
by lugg 7y ago
Yea except you lock your users at an old version, for what? Are you supporting old versions? You don't have to break backwards compat to release new stuff. It takes some serious design flaws to create a situation where you need more th
266.
by lugg 7y ago
No.. the entire point of a reproducible build is so that you can rebuild the same thing given the same inputs across the world different servers. Testing that md5sum(software A) works just like md5sum(software A) is just pointless?
267.
by lugg 7y ago
> People ignore deprecation warnings, so the best way forward is often to break compatibility. People don't ignore deprecation warnings, they vehemently disagree with their existence. Why the fuck are you taking functionality away f
268.
by lugg 7y ago
> Breaking compat on accident happens. Semver would be what? Tests should catch it. Mine or yours. > Bad pushes and releases exist. Semver would be what? Tests should catch it. Mine or yours. > Unpatched bugs in latest. Semver wou
269.
by lugg 7y ago
This is my issue with semver. I don't care about minor non breaking change, just give me the latest. Breaking change is the only thing I want to know about so realistically I only need to worry about major version updates right? So lib
270.
by lugg 7y ago
What is the point of a reproducible build if you need to rebuild it to test its the same?

More ›