We don’t expect you to see that lag. Other users don’t see it or haven’t reported it. What region are you accessing in and how did you generate the result?
It's not that simple, I doubt the boomers working at Google now are the one creating problems and preventing the company from moving forward.
When you see how much stuff they did for ahead of their time ( Big Table , Piper etc...) and now the same tech is being ported to the cloud.
My point here is to say that it's a mentality issue rather than an age issue. If the companies you are working did not invest to transform you and to make you adequate toward current society , you are going to slow down your company otherwise you'll be just fine.
>I’m also tired of all of this inexact labeling of “generations”
The age group are identified page 3.
I personally consider this labelling accurate , but as you mentioned it "boomers" are okay to label others but not to be labelled themselves.
Tech is a bit of an exceptional situation since it’s extremely dynamic and growing, plus there are a lot of youngish people in the upper echelons. I’m thinking more of older, more established industries, which are what the vast majority of people work in.
That’s not what I meant regarding the age. I mean that the same labels are often applied to different age groups; there are multiple definitions. And also, the labels convey a kind of cultural significance that I think distracts from the more important differences. It’s easy to say that “Millenials deserve everything they get because they’re lazy and entitled”, not so easy to say “Young people deserve everything they get because they’re lazy and entitled.”
Is there any plan to make this a partner product ?
It's limited to 10 Concurrent Build for obvious reason, making it impossible for startup who want to create CI services on top of this product due to limitation.
>reading reviews to figure out which listings are noise with fake reviews and which ones are for real
I thought I was the only guy looking for patterns in Reviews and grammatical style to eliminate fake reviews.
Amazon has an insane amount of traffic making it the ideal choice for Chinese electronics makers who have lived or studied to america. They understand western marketing and psychology and it's fairly easy for them to manufacture clones of something that works really well in those countries at lower cost. The products are often flooded with 5 stars rating , mostly incoherent.
It gets especially difficult with dynamic content or when trying to scrape sites written on very heavy frameworks like ASP.NET Webforms that require passing the view state with every request. I made a calendar aggregator for adult hockey times in my area that scrapes rink websites[0] and it was far more difficult than I had thought it would be because of the fact that the rinks all used Telerik Webforms controls to do their calendars. It turned a 30 minute job into a 2 hour job.
> not actually make them on your OWN fork? Clickbait, gross.
Yup. Something like :
> You have bugs in your codebase of 1M+ line, you want to fix them ? Buy my proprietary software for 30$/Month per user , which was built 100% on open source tech obviously.
Getting traffic using linting issues from a large codebase to promote a proprietary software , Outrageous.
I'm an SPA Lover ( Angular , Vue ) , but still most of the points raised here a coherent from a back end perspective.
That said , a lot of the arguments are basically summed up as :
"I don't like Front End Dev. because it's not as mature as Back End".
I will not lie on this point , JS is a fast evolving ecosystem that sometimes has issues to stabilize. Hence , there is a lot of marketing and self promotion mixed with frameworks sometimes ( Growth Hacking ) pushing for unnecessary tech that dies a few days after they have leaved the Github Trending page.
For beginners , when a framework reach a certain threshold ( Github Stars most of the time) they feel like they should hurry and use the framework to stay relevant while most of the time they don't need to and the tech is just fluff.
My point here is very simple, you are ROR or Django or ASP.NET dev and you love what you do ? As long as you find jobs keep doing this , don't bother with Full Stack Fluff.
Now that said , I can only encourage the author to do the Angular or Vue tutorial to discover something different. Rails is great ( it's empowering a lot of website Github , Airbnb etc... ) but SPA are different and when used properly it's hard to go back , the experience is delightful.
Most importantly we are getting closer to the serverless era where backend will be completly different from what it is compared as now, and SPA and SSR will likely be the standard in the future.
> I don't like Front End Dev. because it's not as mature as Back End
No, he says don't do FE and BE when the tools for back end-only (well, Rails is full stack, actually) are so useful and productive. And in the rest of your comment you seem to forget that a front end is completely useless without a back end.
> you are ROR or Django or ASP.NET dev and you love what you do ? As long as you find jobs keep doing this , don't bother with Full Stack Fluff.
Rails is the "Full Stack Fluff".
> SPA and SSR will likely be the standard in the future
How, exactly? What serves your SPA? And who is using "serverless" for anything other than querying other backends (eg Slack bots) or accessing AWS services? I mean, sure, it's nice to not have to stand up a server to resize images coming from S3 but it's hardly going to replace, well, servers. You couldn't implement even the simplest CRUD app.
Uh, you can definitely implement a standard CRUD app with one of the serverless platforms. You can even throw an entire expressjs application into a lambda function with minimal modification if you want.
using lambda and its equivalent is - in my understanding - the definition of serverless. You might not be able to utilize the biggest advantages of serverless infrastructure if you combine it with a standard ACID database backend, but it should still be a serverless deployment.
That was one the clearest guideline description I've ever readen in my life.
Obviously I'm not surprise this was written by an Engineer , it's very clear about what to do and what not.
Usually trainings and guidelines made from Designer are useless to developer , they talk about emotion , colors , moods etc... Which is key for marketing and UX but does not help a developer improve it's skill in UI .
Skill in UI, or if something should work generally for everybody, or optimized for a specific audience, is audience dependent.
Design is basically cultural anthropology, extracting real world types and positioning products to adress those types.
Technically it's tough to sperate both worlds, because layout (grids) and behavior (transitions, animations) have strong stylistic implications. This then means that a developer skilled in UI (making it work generally) can't adress specific audiences, most likely racing to the bottom (too many others doing the same and competing for the same general audience).
The point of this article wasn't self-promotion at all, and I certainly mentioned the similarities between Flutter and React. The point is to highlight the differences, and that when using Flutter, you need to keep said differences in mind.
EDIT: I'm not so sure as to what you mean by "staying at the surface," though - I included examples of patterns that are common in React, their analogues in Flutter, and the reasons why said patterns may or may not apply well in Flutter.
Tried FaunaDB few month ago the latency was beyond 200ms for a simple a read , and beyond 600ms for an insert.
Would not recommend it at this point.