4,485 karma · joined June 1, 2012
80 seems good to me.
This may not be news to developers, but might be useful for broader company discussions.
Or what if I start taking notes on some random subject for fun, and eventually I write and sell a book based on them? All of a sudden I need to start paying a yearly fee?
It's not a prohibitive amount of money, but I'd be much happier with paying a one-time fee for the current version, then buying future versions if I choose to.
Yes, and there is some correlation between age and seniority. If companies are so eager to hire senior developers, they might consider the preferences of candidates who have been working long enough to fit that description.
You decide that B has to compete with A on talent, but A doesn't have to compete with B on price.
Does that make strategic sense?
Companies: "I don't have to pay you $big_city rates because you live in $small_town and nobody there will offer you $big_city rates."
Candidates: "I don't have to accept $small_town rates because I work remotely and can work for a company in $big_city."
OTOH, your applicant pool is limited only to the time zones and legal jurisdictions you're willing to hire from. If you're office-based, it's limited to those who can reasonably commute there.
Agreed. But the reverse is also true: it's harder for people to interrupt you.
Yes and no. The larger the number of dependencies you have, and the larger number of maintainers that are behind them, the more chances you have of one of them containing malicious code.
I think you're pretty safe from Phoenix or Rails or NodeJS getting owned because so many people work on them. But one of the thousand small packages you use may belong to someone careless or malicious.
However, 1) you can add custom JS using LiveView's hooks, which might be enough for very simple offline behavior and 2) many SPAs don't work offline either.
If offline support is a major part of your app's design, LiveView isn't a good fit. But you could still use Phoenix Channels (the building block underneath LiveView) to provide fast push updates to your client. See the channels docs for an idea of how they work - https://hexdocs.pm/phoenix/channels.html
I would caveat that in a couple of ways.
First, suppose you have a web app where some requests involve heavy number crunching and others don't. In web frameworks where 1 request ties up 1 OS thread, a burst of heavy requests could gobble up all your available connections. Phoenix would use one cheap BEAM process per request, and the BEAM's preemptive scheduler would ensure that other requests are answered in a timely way and that all the heavy ones continue to make steady progress. So although the heavy requests might be completed more slowly than in another language, the overall system would remain more responsive.
Second, if you have need for heavy computation or data structures that work better with mutability, it's possible to (eg) use Rustler (https://github.com/rusterlium/rustler) to implement that part in Rust. See https://github.com/rusterlium/rustler for a story about doing this.
To expand on your workload description: things like waiting for a database query or an API result are smoothly handled in this paradigm; the process goes to sleep for a bit whle another request is processed.
If your workflow is like a delivery truck which makes a lot of stops, "faster trucks" doesn't help much with throughput. "More trucks" is better.
See the architecture of Phoenix Channels (which powers LiveView and other websocket-based solutions in Phoenix): https://hexdocs.pm/phoenix/channels.html
And to enable this, the site only needed to create one high-resolution image.
Seems like a victory for loading speeds, for low-bandwidth, and for content creation.
I think FLIF looks incredible.
"Consenting girl" is a contradiction. A child cannot legally give consent for sex. If he knew she was underage and if he had sex with her anyway, that was criminal.
Several possible issues there:
- If the session is large, it eats space on the user's machine and bandwidth in requests - The session can't be shared across devices - Security concerns. You don't want to trust the user to tell you what their current state is - especially if it's "I have this much money in my account" and the like. Even if you encrypted the data, they could resend the same state at a later time - "oh look, I have a full wallet again!"
You're much safer if all the user sends is "here's who I am" and every bit of associated information is under your control server-side.
I disagree. Unless the candidate desperately needs this job, he/she can walk away. The candidate is free to consider "company won't bother to answer my questions at the point when they have most reason to be nice to me" as a bad signal.
> I am specially referring to companies that don't really have to care about your feelings towards their interviews
"This company doesn't have to care about my feelings because they are huge and have lots of applicants and a giant incessant interview machine chugging through them efficiently" is certainly something I'd consider in whether I want to work for them, because it tells me I'd be a cog in a machine. (And if enough people consider that, perhaps they will have to care.)
To the parent question: I wouldn't ask a whiteboard question exactly, but I would certainly ask some questions about existing architecture and rationale so I have an idea what I may be working on.
A basic HTML document with CSS styling will adapt beautifully to any screen and requires very little CPU or memory. Write once, view on every device with a browser. Publishing content is also part of the original vision of the web, and luckily HTML forms are also accessible to any device.
Yes, you want to write apps, and perhaps that requires more from a device, and maybe you don't want to cater to poor Indians. But lots of sites are sending down 3 megabytes of JS to display an article and run 48 ad trackers. That's a crappy experience even on my smartphone and decent WiFi.
I'd also wager that there are many, many "apps" you could write which could be 100% server-side rendering and simple markup, and which would be super useful in the developing world. Think Craiglist and Ebay - the kind of applications that help people share their location and agree on prices of goods.
The "use anywhere" promise of the web is easier to keep if you lean on the web's fundamentals instead of writing a browser to run in the browser and shipping it to every user.
Also, if the employee has very marketable skills, they may be happy to leave a job whose hourly rate has suddenly dropped.