at companies making the largest AI investments, entry-level head count grew by 12% over the two years following AI adoption.
Conventional wisdom is not wise
at companies making the largest AI investments, entry-level head count grew by 12% over the two years following AI adoption.
Conventional wisdom is not wise
Lack of standard definitions makes it harder for learners to navigate options and for employers to assess value
This assumption needs to be validated. Would standard definitions be a silver bullet for learner navigation and employer value? To wit: We have standard definitions for degrees and yet the navigation and value problems persist in that domain. What if the more important issue is not what to call these programatic containers but rather how to describe the contents of what they contain?
as a more experienced user I know one can navigate much more quickly using a terminal than using the hunt and peck style of most file system GUIs
As an experienced user, this claim strikes me as false.
I often start in a graphical file manager (nothing special, Nautilus on my system, or any conventional file explorer elsewhere), then use "Open in Terminal" from the context menu, precisely because of how much more efficient desktop file browsers are for navigating directory hierarchies in comparison.
NB: use of a graphical file browser doesn't automatically preclude keyboard-based navigation.
You might have heard of the old saying “Rollup for libraries, Webpack for apps”