Electronics > Beginners
When you follow the schematic but it doesn't work
tooki:
--- Quote from: james_s on July 26, 2018, 04:44:23 pm ---
--- Quote from: tooki on July 26, 2018, 04:13:02 pm ---There's all sorts of non-programming IT. Hardware, business analysis, UX design, it goes on and on.
And no, for most programming, you don't need to know the machine abstraction in any great detail. That's literally the reason for having the abstraction.
--- End quote ---
Seems the trend in tech lately has been to hire programmers to do everything, product design, UI design, QA, it's probably why software quality has taken such a dive recently pretty much across the board. My first iPhone was rock solid, polished, slick UI, everything worked. The one I have now is very buggy, inconsistencies in the UI, reminders often fail to pop up or get out of sync between the lock screen and the reminder menu, even the built in apps crash. It's very obvious that parts of the UI were designed by people who have no business designing a UI, and there is no longer sufficient QA. This is only one example, I see it everywhere.
--- End quote ---
Hear, hear! In UX (my field), we call those "UX unicorns": people expected to do usability research, interaction design, graphic design, and coding. Sure, you can find people who "can" do all those things. But I'll be damned if I've ever seen one who can do all those things well!
As for quality: thank Agile for that. Agile itself is a reasonably sound methodology (not highly sound, just barely acceptable). But it's still a formal methodology. But tons of places say they're going "Agile", when in fact they're just going "free-for-all", with no formal test cycles, just devs pushing untested code to production… (I've worked in customer/tech support at a software company that did that. What a goddamned nightmare…)
--- Quote from: james_s on July 26, 2018, 04:44:23 pm ---Programmers should be spending their time programming. Other positions should be filled by people with expertise in those areas. "IT" is not a one size fits all field, automation is not a replacement for professional QA, engineers tend to be lousy at UI design, and developers who like writing code better than working with people make lousy managers.
--- End quote ---
Exactly. I think a lot of folks (even in IT!) assume that IT means programming, and that all areas of IT must include it, and that's just not true.
bd139:
Thats what everyone said until their job turned into three lines of python. :-DD
I agree but the focus is on automation. The whole point is that if a task is to be done regularly then automation has a cost benefit. Even our analysts automate with specflow and our project management team automate their workflow with python. Our graphic designers automate their pipelines with various tools (I don’t go there myself). Our management team run automated reporting they built themselves. Our customer support team drive our public API to resolve issues with their own scripts. Our entire front to back end process stack is automated. All our marketing is data and code driven.
Everyone is a programmer if they like it or not. We destroyed all of our competitors because of automation.
We’re “a loose interpretation of agile” but continuous delivery focused. Everything from code to production is automated.
IanMacdonald:
--- Quote from: bd139 on July 25, 2018, 10:40:48 am ---They're teaching C# and nodejs at my local college and their staff have absolutely no fucking idea what they are doing. We have had a couple of their "graduates" in on trial and we're basically having to get them to unlearn a lot of stuff. I mean you don't write an OO program entirely in static methods ffs. But that's what they told us. Seriously, no.
--- End quote ---
Colleges seem to have an obsession with OO programming. While it does have its uses, it's an extremely inefficient way of doing things. I also find it weird that they insist on using C, basically a stripped-down language designed to keep overheads to an absolute minimum on puny hardware, coupled to so heavyweight a paradigm. Kinda seems like two mutually defeating objectives, does it not?
You have to ask whether it might not be better take the middle ground and use a less stripped-down procedural language. :-//
That is even before you take into account the serious security issues of C.
bd139:
Not really. OO languages scale up to huge projects a lot better than non OO ones. I’ve never seen a large successful procedural or functional project. They all turn to shit way earlier.
I think you need to at least play with assembly, learn C, learn Java properly and learn a functional langauage properly. Then go and use whatever you feel fits the problem.
GeorgeOfTheJungle:
Ryan Dahl is back, with a new node.js
https://github.com/ry/deno
https://youtu.be/M3BM9TB-8yA?t=1s
We start again from scratch!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version