Yes, but if I'm working on image processing, videos related to that go back many years, and things covered in earlier videos are often not covered in later ones.
Other that than, let's agree to disagree. Maybe you're right, maybe not, we'll see :)
1,169 karma · joined August 15, 2014
Yes, but if I'm working on image processing, videos related to that go back many years, and things covered in earlier videos are often not covered in later ones.
Other that than, let's agree to disagree. Maybe you're right, maybe not, we'll see :)
I wish OpenCV made use of the GPU and vector hardware on phones. Is there an alternative to OpenCV that does?
So would I, as I mentioned in my reply to you. It's easy to propose ideas without regard to cost like a "minor enhancement" that takes 6 person-months.
It may also take your focus away from becoming good enough in your primary skill to pass the hiring bar. If you can do engineering, marketing and UX design, but you're not good enough in any of these fields to get hired as an engineer, marketer or designer, you're in trouble.
I think it's better to pick a primary field, get to the top 10% in that field, while being good enough at a secondary skill. For example, "I'm a great engineer, but I can also get you your first 10,000 users on the marketing side. I won't be as good as a dedicated marketing person, of course, but I can get this job done." Then you can apply for an engineer job, convince them how good an engineer you're, and then convince them that you also have some design and marketing skills.
(10% was an arbitrary number. The point is that your skills in your primary field should be good enough to clear the bar.)
Another question: as https://news.ycombinator.com/item?id=18484883 says, would it help to rewrite your CV to highlight what the job is looking for? Again, if it's an engineering job, talk about your eng accomplishments in great detail, with perhaps only a bullet point for other skills at the bottom of the resume?
As https://www.kalzumeus.com/2012/01/23/salary-negotiation/ says:
> Did the solicitation for the job say “We are seeking someone with strong skills at scaling traffic in a fast-moving environment”? Pick out the key words. Scaling traffic. Fast-moving environment. “Scaling traffic” doesn’t sound like how I’d phrase it if I were writing or speaking for myself, but if you’ve just described your need to me as scaling traffic, by golly I will tell you how great I am at scaling traffic.
Are you also good in your primary skill? Is it like 100% of engineering (say) + 20% of UX design, or 60% each of engineering and UX design? In the former case, one will clear the bar for an engineer job post, with your UX design skills helping to position you above other qualified engineers. In the latter case, you may be judged unqualified and rejected.
And what do you think about related skills, like UX design or marketing in addition to programming.
It seems that people are coming to you to help estimate how long an idea takes to implement. If that's the case, I agree with everything you've said.
But if they're proposing an idea, say a new sign up form to increase conversions, phone number validation is an irrelevant detail to worry about at this point (unless that was a significant problem with the old sign up form).
But:
In this example, unless not handling international phone numbers leads to failure of the project, that can be handled later, say once the project is approved and time estimation is being done. If I'm building a notes app, and someone is proposing a new sign up form to increase conversions, and it has a phone number field, handling international numbers is the last thing to worry about at this stage (unless international numbers are a significant problem with the old form leading to abandonment).
We shouldn't doom good ideas with irrelevant details, which are absolutely relevant later, but not now. Product development happens in phases of increasing fidelity, and issues need to be brought up at the appropriate time, not too early, not too late.
It will take off if it's better bang for the buck at any market segment. That can be Rs. 100 a month or Rs.2000 a month. If it's better than the alternatives people can get at that price, they'll use it.
That's viable for consumers only if it's shared, like by providing an open Wifi access point to everyone around it, or via Ethernet in an apartment or a small village.
I don't mind the latency of today's fiber or cable Internet, and if it's problem, it can be solved by moving servers closer to users.
That is, what if, instead of bypassing the fiber backbone, Starlink just tried to connect everyone to it? Because I'm assuming that sending a terabit of data between two major cities, like Chennai to NYC is going to be cheaper via undersea fiber.
While you may be right regarding the context in which you said this — satellites — as a blanket statement, that's not true: my smartphone loses Internet connectivity when I leave my house, and takes a few seconds before it connects to the cellular data network.
I'm surprised that phones don't establish a backup 4G connection when Wifi signal strength decreases suddenly, but before it disconnects. This has been talked about for years, but for whatever reason it hasn't been deployed or doesn't work well, at least with Android P.
This is a diffuse impact, rather than localised — if waiters are required to be paid more, some factory workers may lose their jobs.
After experimenting, then we as a society can decide not to permit something, not before.
As an analogy, what if burning fossil fuels were banned worldwide in 1900 because people were too conservative about pollution? We all agree that pollution is bad, but we should be willing to permit some amount of negative side effects if we want progress. Otherwise, we'd still be living in medieval times.
Is a pure software solution even reliable enough under these conditions? Slowness can be worked around by doing it in the background, and you get a notification when it's complete. Some people would be okay if that's the only way to get photos they wouldn't otherwise be able to get, short of buying an SLR.
As another example, we put the terms and conditions ("subscription will renew unless canceled...") in a web view. Apple rejected us telling us to put it in the binary. We put the HTML locally, but still in a web view to display it. Is that considered part of the binary? Apparently not. We then made it plain text and didn't use a web view. But it wasn't okay, to have this behind a button. It has to be on the subscription screen. However, having it scroll off the bottom of the screen is apparently fine.
This is why it's frustrating to develop for Apple's platforms — you have to play a guessing game, where each round results in a rejection and multiple days of turnaround time. I'm considering making our app paid up front to bypass this bullshit.
Since the iOS dialog box has all the necessary information, and Apple can present it in a way they consider transparent to users, why make apps redundantly display the same information, and then reject them? The sensible thing to do would be to ban only apps that give misleading information, like Rs.10 if it actually costs Rs.100. Not giving any information in your app UI like price, duration, terms, should be fine.