5 ms·
Your job is to make money for the company. Your job isn't to build the smoothest, most optimized, experience for your customers. It's to build features custome
by arcticbull 6y ago
Your job is to make money for the company.
Your job isn't to build the smoothest, most optimized, experience for your customers. It's to build features customers want or need, which in turn create value for your employer. This generated value pays your paycheck. Of course if you do a bad enough job, it's counterproductive, but to the extent it's not bad enough your job is to focus on features and development and not on optimization. Once performance is bad enough, your job becomes optimization -- via instrumentation, measurement and profiling.
Every minute you spend waiting on a build or waiting for an app to launch or waiting for some long-running task to finish is a minute you're not creating value. Compounding this problem, it impacts morale if you spend your day looking at spinning beach balls while your boss won't get off your back about when you'll be done.
This is your employer's perspective, more than likely.
[edit] Another way of looking at this is to say that you and your customers are doing different jobs. You have all the extra cpu and memory overhead of developing a product — all they have to do is run it. By definition your workload is more demanding.
- MattGaiser 6y agoThat and the cost of distractions waiting for a build. I used to work in a place where a build would take 3-4 minutes. In practice, it often took 15 as I went to Reddit or Hacker News or chatted with a co-worker and then had to remember what it was I was doing.
- est31 6y agoI think one needs to differentiate between building and manually testing the app. Running the build on a fast machine greatly benefits the development cycle while the tests are harmed because you don't test close to your users.
- pishpash 6y agoThere used to be a time when you ran development/debugger on a different machine than the one running the application. Developers having fast machines for work should have absolutely nothing to do with not properly testing for user environments. That's just poor engineering, which unfortunately pervades today.
- iainmerrick 6y agoThis is still the case in mobile development. A good setup is to build on a fast expensive PC and run your app on an old cheap phone.
- saagarjha 6y agoI think that's part of the argument for this, yes–a company that doesn't provide their developers with the best tooling is hurting themselves because they're wasting their developer's time. But I'll argue that the opposite can be true as well! By using a machine that is far removed from what your customers are on, can you really test their user experience? And, this is a personal anecdote of course, but sometimes having fast machines can paper over problems that you should really be addressing: I had a coworker once who temporarily used a fairly (~7 years) old machine to do their development work until they could get something newer to work on. During that time I noticed that they would take a while to make minor fixes after reviews. I asked them why and they told me that they would make the change and then they'd build it and it was taking dozens of minutes–it turns out that there was a creeping dependency tracking issue in the build process that nobody had bothered to address yet because it didn't seem like a huge issue on our normal machines. But fixing it certainly got his turnaround time way up, and the CI machines really liked the change too ;)
- virtue3 6y agoWhy would a developer be in charge of testing the user experience from the user perspective? Either have good relations with your end users or use QA with properly outfit machines. Or you should -know- what specs your users are using (this is really not hard) and optimize for that. You can get chrome to degrade network performance etc. It's not easy to downgrade machine performance tho.
- astrange 6y agoYou can simulate a slower machine with a VM, or by disabling extra cores and memory on your dev machine, or by running your app off a slow external drive. It's not as easy to do this as it could be, but it's not that hard either.
- wwwhizz 6y agoSimply run your app in a VM, that should degrade performance, customizable as well.
- mister_hn 6y agoWhat about Cloud Environment? Do you know that writing code efficiently can also save money for the company? If you try to write code that burns bandwidth or CPU cycles without even attempting to optimize it, it's gonna cost you an eye at the end of the year. Software optimized for the slowest hardware possible actually does saves money, which helps also to reach the goal of doing more money, since more hardware is being supported, not only the cutting-edge one. I've seeing now this infamous trend also on Android Phones boosting 90-120 Hz screens. If applications get optimized to run on these phones, whose CPU is also strong, obviously older phones are suffering and become sluggish. Seriously, try to write code as your target platform is a Raspberry Pi 1 model. If works on it fast, it's going to be fast everywhere
- exged 6y agoThat's true, but it really depends a lot on the kind of software you're writing. If you're Google or Facebook and make fractions of a cent per pageview despite doing an enormous amount of computation then optimizing your code and infrastructure is very important indeed. On the other hand someone like Airbnb is very likely to make tens or hundreds of dollars off a handful of pageviews, so cloud costs are much less of a concern.
- qz2 6y agoYour job is to make cost effective decisions actually. And that’s a long game not a short game. If you fail to make those consistently you end up with large infrastructure bills and unhappy customers eventually.
- astrange 6y ago> Your job isn't to build the smoothest, most optimized, experience for your customers. That is literally my job! You should have someone like that too, or else you'll end up shipping an Electron app like Discord does.
- nmfisher 6y agoDiscord just hit 100 million active monthly users, kind of proving OP's point. Using Electron enabled them to ship quickly and deliver on important features to users.
- tpush 6y ago> [...] or else you'll end up shipping an Electron app like Discord does. And get to dominate their market niche? People got to realize while native apps are nice and all, there is absolutely zero evidence that going native vs cross-platform improves any metric a business actually cares about. Users are flocking to cross-platform apps in droves! Vocal message board users screaming their preference for native apps are not in any way a significant share of the actual market for these applications.
- yellowapple 6y ago> Users are flocking to cross-platform apps in droves! I seriously doubt the use of Electron is what's driving that. And it's also worth remembering that "cross-platform" ≠ "bundle an entire web browser in the app". Qt exists, as one of many examples of application frameworks/toolkits that are simultaneously cross-platform and native.
- tpush 6y ago> I seriously doubt the use of Electron is what's driving that. It is indirectly driving that. Using Electron instead of other cross-platform frameworks like Qt allows one to work faster since you can apply webdev knowledge, and that directly leads to features that users actually care about being delivered faster.