3 ms·
The interesting thing to me about this as a programmer is that it really looks like a spec. There may be even bored programmers who read this on HN and have al
by ilaksh 9y ago
The interesting thing to me about this as a programmer is that it really looks like a spec.
There may be even bored programmers who read this on HN and have already started building it.
It would be interesting to see how many changes were made to that spec by the end of the development process.
The trickiest part to me is the idea that regardless of what computer you put the USB stick in, it just immediately loads the program. Can you even really be sure that will happen if you restrict it to the last few versions of Windows?
So that right there is one of the most challenging aspects of software development -- when a big part of the concept is something that either isn't actually feasible as stated or you are not sure is possible. Which is really common because most projects are not driven by programmers but by non-technical people.
What it seems like most programmers will do is to try to find a clever way to gloss-over this 'little detail' about how they don't know how to be sure that a program will immediately open with no effort once the USB stick is inserted. The issue with that is, if they leave it a little ambiguous, and then it turns out that whoops, it never opens on his Macbook or requires him to manually launch it.. then his super-easy program is not nearly as simple as he imagined.. if the instant launch was a big part of it. Then the average programmer would just say "well, I told you I wasn't super sure that it would work exactly as you liked" -- when really he barely mentioned it and the guy didn't believe him.
Maybe some programmers are good at handling this -- I think you really need to find a slick way to convince the guy that he never really needed or wanted that instant open USB thing, or that having to double click after it was inserted is exactly the same. Kind of about psychology as much as anything.
- marmaduke 9y agoYea I started reading it that way (as a spec I'd implement) but got hitched on the auto launch part. if a single double click was allowed, it's feasible but requires choosing a launcher/file for the os
- deleted 9y ago[deleted]
- empath75 9y ago> The trickiest part to me is the idea that regardless of what computer you put the USB stick in, it just immediately loads the program. Can you even really be sure that will happen if you restrict it to the last few versions of Windows? It's a textbook example of an x-y problem. He wants to be able to work anywhere. He thinks the right way to do that is a USB drive. The actual right way to do it is as a web app.
- neogodless 9y agoYou're right that suggested solution might not be the best, but the problem is trickier than you'd think. For example, I know writers who like isolation. Not just being alone. Going to a remote place where they have no connectivity to the outside world whatsoever. So while software that lives and connects to the internet gives a user "a lot of devices in a lot of places" to do their work, it does not give you the "ability to work anywhere." Now you have to make sure you solve the problem of - having the software and the user's work in progress (WIP) on whatever device(s) they take out of internet connectivity, and also making sure the updated WIPs get pushed back to the internet as soon as they reconnect. We could try to simplify the problem with an assumption, like only run the software one device (instead of only one USB stick), but you've created new limitations to how they work. Maybe they get by with their mini laptop in the cabin, but they prefer a different computer at home. The USB works better with the multiple locations and, in theory, devices, until you get to the multiple OS (and releases) problem discussed in the parent comment. So while it's not the job of the product owner to use the solution presented, it is their job to think about why that solution was suggested, and run their own proposed solutions through those reasons.
- gwbas1c 9y agoBut he wants the application to disable the internet! It's more an example of a customer needing guidance from a professional. In this case, part of deciding if this is a good project to work on is explaining the tradeoffs and seeing how the customer navigates them. If the customer really wants to "have his cake and eat it too," then walk away! If you tell the customer, "computers don't automatically run applications on USB sticks because then they would get hacked," and the customer doesn't understand, then run away! Otherwise, this is a situation where the customer needs to understand the tradeoffs among a web application, desktop application, and tablet application. If a desktop application is preferred, then there are very significant tradeoffs with applications that can run off of USB sticks, versus tiny installers that will only run on a recent version of Windows, versus an installer that will work on Windows XP. This is also a situation where a statement like, "an application that runs off of a USB stick is very challenging, and is limited on what it can run on. This would be a major distraction. Can we limit this to Windows 7 and Windows 10 with recent updates? Otherwise, we can put an installer on a USB stick, but it might be very large in order to support older windows without updates. Would a web-based application be better? You can run them in full-screen mode."