3,861 karma · joined December 15, 2010
Cheating.
Before people start booing, let's not forget where this tournament is being held, and all the other nefarious things that country has been up to recently.
It’s just R&D. It’s not an exotic idea.
I’ve always been a big believer in rebuilding your product from the ground up. I think it’s something you should always have going on in the background. Just a couple of devs whose job it is to try and rebuild your thing from scratch. Maybe you’ll never use the new version. But I think it’s a great way to better understand your product and make sure there’s no dark corners that no one dare touch because they don’t understand what it does, how it does it, or why it does it the way it does.
And I’ve always believed that if you don’t want to rebuild your app from scratch, then don’t worry, a competitor will do it for you.
So I agree with every point raised in this article. And I think it does a great job of articulating the issues that often go unspoken. But I’d like to add one more. And for me, this is the biggest issue for any company wanting to rebuild it’s product.
If your sales team has more clout than your designers and developers, then you’re fucked. And in the enterprise software world, this is the norm. An uncheked sales team that get’s whatever it wants has already killed your product and made it impossible to rebuild. Their demands are ad-hoc, nonsensical, and always urgent. So urgent that proper testing and documentation are not valid reasons to prevent a release. Their demands are driven by their sales targets, and the promises they make to clients are born out of ignorance of what what your product does, and how it does it.
This is not true of all companies. Many companies find a reasonable balance between the insatiable demands of a sales force and the weary cautiousness of their engineers. But if your company submits to every wish and whim of your sales team, and you attempt to rebuild your product, then you’re screwed.
Understandably, few people like that advice because it doesn't make life easier. It does make your product better though, which is really all that matters.
They don't. And when something like this has a connection to a company like Google, people simply don't question it.
So, anyone got a non-paywalled version of this?
Much like regular debt, if you don't repay it, you go out of business and end up penniless.
1. Don't fear the refactor. 2. If you don't want to rebuild your entire application from scratch, don't worry, a competitor will do it for you.
There's nothing wrong with creating something in increments. It's the fear of revisiting something that destroy's a code base.
It was conspicuous. I asked is he'd asked me that because of GDPR. He said yes. I said no.
The kind of law making you’re implicitly advocating is tantamount to despotism. Drafting a law that outlaws islam might well be clear in it’s wording, but it needs to be tested against the law that allows freedom of religion, freedom from persecution, and a ton of other laws no doubt. The claritiy of language with which a ban on islam is articulated is all for nought if it’s contradicted by, and incompatible with other laws.
Although, GDPR has been explained very clearly. And we’ve been given a loooong time to digest, understand, implement, and question it. I don’t think any reasoable person can make a compelling case against GDPR. But unreasonable people can, and as we’re seeing, they will.
But yeah, seriously, how hard can it be to make AirBnb? It's just a couple of tables in a database, a HTML form and a jQuery image gallery.
Software is meant to do things for you, but so many software developers think software is there to stop users messing up their database.
No one really knows wether UBI will be a succes or a failure. But then no one knows wether any policy will be a success or a failure, and there will always be supporters and fetractors on either side.
Ultimately though, all that really matters is that government takes action that it believes will make society better. That’s it’s purpose. And if government believes UBI would be a net good, it should do it.
They seem to be having their cake and eating it. You hear the term "disruption" all the time from tech companies, and you'll hear tech leaders wax lyrical about their vision for society and how their work/product/service is shaping that.
Recent events have outed these people for what they are. Self serving profiteers who only care about how society can help them, and have little regard for how they can best serve society.
While shady corporate megalomaniacs are a problem, they are by no means unique. What leaves such a bad taste in my mouth however, is the way tech billionaires are so eager to project the idea that they're benevolent agents of progressive change, when really they're not and they're not even trying. They've been dining out for free on goodwill for too long. Now it's time to start paying the bill.
https://github.com/reactjs/redux/tree/master/src
The largest and most important part is CreateStore, but at 250 lines long (mainly comments), it's shockingly simple when you take a look at it.
Once you commit to a config based approach, you're basically closing the door to a future you can't imagine yet. I'm so tired of this short-sighted obsession with configuration some developers seem to have.
I think the author has a myopic vision for where Redux should go.
Dijkstra’s algorithm is on page 36 and explained in 8 paragrpahs.
Having worked both scrum and kanban, I feel kanban is better for both large and small teams, so long as the team puts some thought into which items each person takes out of the backlog.