BigJono

33 ms·

301.
by BigJono 6y ago
People get stuff done in JS by sidestepping all the bullshit. If you keep your tooling simple and use a minimal amount of dependencies, then JS is one of the languages/environments with the least bloat, not the most. The big problem JS
302.
by BigJono 6y ago
I think chess.com has something similar too, but not sure if it's powered by wasm. If it's not, I'd be interested to see a speed and feature comparison between the two.
303.
by BigJono 6y ago
True. One of the reasons I prefer React over others is it gives a good standardised base to work from, but you can still compose the right set of tools for each project around it. Of course you can still fuck that all up by starting a proje
304.
by BigJono 6y ago
IMO this whole thread suffers badly from differing definitions of 'framework'. The 'framework' of your app is a collection of patterns and interfaces that allow you to implement your actual features as easily as possible
305.
by BigJono 6y ago
> I would tend to think if you built your own framework the right way you would end up looking a lot like... an existing framework. Nope, existing frameworks are designed to solve the problems in 100,000 different applications across eve
306.
by BigJono 6y ago
I wonder if there's any Japanese sites out there that fully use the traditional style? Text top to botttom, right to left, and with the horizontal axis unbound (to the left) instead of the vertical.
307.
by BigJono 6y ago
That doesn't work if the consistent behaviour is completely useless. If double click selected English tokens grouped by which half of the alphabet they came from, nobody would ever double click anything, they'd just click-drag hig
308.
by BigJono 6y ago
https://www.youtube.com/watch?v=KavEoHGiU5I This is my favourite one.
309.
by BigJono 6y ago
As a seasoned bogan, I reckon he's a bit over the top. I think if he cranked it down about 20% he'd sound more natural. There's a few 'fuck's in his videos that don't naturally fit into the sentence.
310.
by BigJono 7y ago
This is why I like to estimate on a more macro level. Define features loosely, with a few lines of text about what they are and how they relate directly to a business goal (how will it make money, make the product better etc), then as a dev
311.
by BigJono 7y ago
> just a symptom of having too many nonprogrammers around. Will resolve itself. Parkinson's Law doesn't get enough of the blame for bad dev environments. It's so easy to feel like you're doing 40 hours of difficult, i
312.
by BigJono 7y ago
The mistake here is making your measurements too granular. What happens is the board meets, long and medium term plans are made, etc etc. That's all good. Then what happens is every level of management calls in the banners and forces t
313.
by BigJono 7y ago
I wonder how many CEOs have said something like this just before a "bunch of hackers" has eaten their lunch and decimated their stock price?
314.
by BigJono 7y ago
I assume 'talkers' means people that only talk. OP isn't making a case for or against planning, just saying that if you're taking a small team approach, once the planning is sufficient, the people who do the planning a
315.
by BigJono 7y ago
I think OP is describing the winning formula for a productive team, but he's attributing it primarily to the wrong factor. Shipping often increases quality if you're getting good feedback from users and acting on it. But it's
316.
by BigJono 7y ago
That's true. I think they're still needed in some capacity though, just in lesser quantities than is usual, and with more focus on supporting development and more of a quality over quantity approach. The devs shouldn't be doi
317.
by BigJono 7y ago
The problem is 100% with the way software is developed these days. Every company trains their staff to be as unproductive as possible with open plan offices, all the productivity is coming from quantity over quality, with every hire and eve
318.
by BigJono 7y ago
That's all true but I don't think it explains the effect GP is talking about. Security aside, I think it just comes down to what the business incentives are for different approaches to software development. To develop good softwar
319.
by BigJono 7y ago
That's fine, but the title of the post literally contains "you will too". The author isn't only presenting an anecdote, they're making a claim that it applies to other's situations too. So I think it's f
320.
by BigJono 7y ago
Your argument is the one that's a strawman. You're assuming that the kind of mistakes that I make while coding are the exact kind that Typescript prevents. Which is not the case. There's more ways than type hints to fail fast
321.
by BigJono 7y ago
I'm sure that class of bugs is relevant for Typescript programmers, because they never develop the skills to not implement those bugs in the first place. If your usual workflow is to defer all of the typing information to the IDE, rath
322.
by BigJono 7y ago
The deciding factor is how complex the code is. You can add a ludicrous amount of complexity into a React app before you've even implemented your first actual feature. People do it all the time. Those people will always get smashed in
323.
by BigJono 7y ago
I believe they do some sort of local batching of transactions then settle them all at once. You can see this sometimes if you go shopping early in the morning and you're the first person to use a particular EFTPOS terminal for the day,
324.
by BigJono 7y ago
I had a lot of trouble understanding it until I read it 5 times. All the words just turn to soup in my brain as I read them... It's like the information density of the text isn't high enough to keep my attention or something.
325.
by BigJono 7y ago
You're misunderstanding what he's saying. He got a 50% cut in salary, but because all of that comes from the higher brackets, his take home is only 35% less. I do the same thing (Australia). Worked 9 months last year and made abou
326.
by BigJono 7y ago
> I've worked at little startups and a medium-sized tech company as well as FAANG. In each case, we spent most of our time working on projects with 2-3 month time horizons. The small and medium companies called their development str
327.
by BigJono 7y ago
> these days, JS ecosystem is getting a bad rap for having such bad code wrapped in neat and easy-to-install NPM packages.) Is it? IME nobody seems to give a flying fuck outside of HN. Much like the PHP days. Or maybe I've never bee
328.
by BigJono 7y ago
Of course, those are good examples. And I do write tests for stuff like that. But it's a tiny, tiny part of what the average front-end web app dev is doing on a day to day basis. My claim isn't that testing is useless. It's t
329.
by BigJono 7y ago
Funny you mention food order apps. UberEats web app is my prime example of how a flaming train wreck can make you a ludicrous amount of money, and how there's almost no correlation between engineering quality (not necessarily product q
330.
by BigJono 7y ago
> The fact that current testing practices are considered "effective" is an indictment of the incredibly low standards of the software industry. This is an interesting one. I first took it to mean 'current testing practices

More ›