Its all relative. There is no baseline for expertise in software. So, instead its whatever self-serving quality some sociopath on the other end favors.
Most of these scandals look like repackaged AI. It’s like there is no real business under any of these with the only real value in raising venture capital.
I am working on a task manager that’s way more informative and resource efficient than the windows task manager and works on Linux. It also provides an informative dashboard for docker containers and web servers with proxy support and preference for streaming sockets supporting http and web sockets over the same ports.
Instead of throwing up an error response wouldn’t he achieve more desirable results from redirecting the address to the same address but without the query string.
All of the conduct, behavior, communications, and so on. The tent city, uniforms, props, vehicles, communications equipment, and more were also completely right.
This is shockingly true. Most newer FE devs I have encountered are mostly trained on the popular frameworks and lack understanding of the underlying fundamentals, e.g., they only know TypeScript + SCSS and some smattering of HTML but more often know whatever templating engine and MVC(ish) backend the framework uses. It’s really helpful to understand what the browser is actually doing and all the “stuff” the framework spits out on the other end.
Modern JS/TS devs probably not, but I wouldn't even call someone a "frontend dev" if you don't know HTML, kind of being a infrastructure engineer and not knowing how any OSes work.
It’s not just knowing HTML as in writing a bunch div tags and patting yourself on the back. If you aren’t able to achieve at least 80% WCAG AA compliance you can’t write HTML.
Most frontend devs have no idea what any of that means. But then it seems everyone who can write 3 lines of code professionally refers to themselves as an ”engineer”.
Yes, it's literally about being able to use HTML effectively and knowing what you are doing, then you know HTML. I'm not sure why you bring up some arbitrary accessibility guidelines, that has no bearing if someone is using HTML correctly and neither would I gatekeep the "frontend" label on some arbitrary "must pass this particular standard", never heard something so outlandish when it comes to who could call themselves frontend developer or not.
I agree with the other comments. Its super cool after it eventually loads.
For real world use I don't think its practical if its only goal is basic browser UX in Python versus JavaScript, but I can see amazing value in this for larger applications written in Python that need to make use of a Python GUI.
Absolutely. This shines when you actually want to display complex / animated / streaming data in larger applications; or if you want to create educative or training material on several pages (i.e apps here).
As an example, I once built an online stock/ticker app with it: smooth real-time updates in a nice plot. It would have been more complex with DOM based widgets (and probably less fun).
Another doom and gloom post about SkyNet killing all the children in AskHN.
Yes, there will still be very many programming jobs for humans.
Yes, AI will eventually kill all the programming jobs staffed by people who cannot program, the pretenders.
Is programming really all about writing code? Yes, mostly. Yes, soft skills and communication skills are more important but writing code is your bread and butter. If you do not understand your craft then those more important qualities don't matter. You have no baseline upon which to exercise those more important skills.
If you are the kind of person who cannot tell the difference between writing original code versus pretender then yes, I would absolutely look for a career change. If you write software as a hobby yet struggle to land a job in sea of pretenders then there is a dim light in your future that will only get brighter with time.
How to identify the pretenders:
* Ask the person to measure something. Provide the means to gather data but not the data itself.
* If they need a magic framework because data structures are scary, such as React because the DOM is a mad bedtime killer in the dark.
* If every decision point is a game of bike shedding or Halloween costume.
* When the goal is to look busy or appear as a hero savior, as opposed to just completing an assignment quickly.
* If tasked to write original work is scarier than death in a Saw movie.
I have nothing that fits that criteria exactly. I still write tests for test automation manually and that should be automated but new tests are only needed as features are created or retired, which is irregular and infrequent.
Throughout my career many people have believed such bullshit illuminated their productivity. What has gotten me promoted in the past was doing the opposite, as in trying to not appear busy. If you have to justify your existence then your reason for existing is not well justified.
reply