88 karma · joined April 18, 2019
I've used it for more than 10 years, and it's my go-to DAW ever since.
I've also seen countless of young engineers starting to welcome managers' feedback and "showing" their will to improve. Then, gradually,noticing their management incompetence (technical and/or managerial) and start "saying" stuff to avoid confrontation.
Self reexamination and accepting feeback is great to improve but what if the feedback is just plain wrong or contradictory ?
A lot a "sayers" in your team can be a red flag for your management skills.
Even if there was not, once a company has eliminated 99% of the candidates and put their mind to hiring you there is a good chance you have a little leverage at negotiating your salary.
I don't think the author work the same jobs than I do.
I totally agree with that proposition. The degree is not a sine qua none condition of competence.
My point was that success stories about kids making a lot of cash on a self taught developer skillset are pure and simple lies. They hide the truth to those who really want to get into the IT industry and make a living with it. That truth is : work your engineering skills if you want to build cools things.
I said make a living. Not get crazy rich. Engineers don't get crazy rich. Salesmen (and salewomen) do.
People that did not have the ressources or desire to go to uni would get a lot more encouragement and from real developer tales : stories about smart engineering, beautiful UIs, dedication to a craft and passion, or even sly hacking.
Instead they read stories about skilled salesmen. The stories are not even that good. Glengary glen ross and the wolf of wall street are much better.
This does not prove you can make money by learning some wordpress overnight but still the article pretends exactly that. The average worker with average sales talent will have to present real skills to an employer to get hired. Those real skills take time to develop. It's evidently possible to get them outside of Uni but it takes times and effort. Guidance by experienced people reduce time and effort to learn a skill. That's the whole point of schooling btw.
Those article say "I taught myself how to code and became rich by offering the world an awesome product". They should be "I'm a very good salesman and I became rich by getting people into buying my software".
That software is maybe good, maybe not. Mostly not. Second law of thermodynamics teaches us that you can't beat a 30 year old experience with an overnight schooling, except if your father is zeus or someone like that.
That degree got me my first job. And the next. I started with zero debt and I do not come from money. I am very grateful for that. I would probably not have attended a 5 year college if I had had to get into debt.
My whole point was that the truth of what it is to code for a living is hidden by those kind of sensationnal articles. Those who want to get into the industry are not encouraged to work on what matters (ie engineering skills instead of fancy frameworks) and end up disappointed with their opportunities or their skill set. CS universities tend to push students toward developping an engineering skill set.
I would really like to see people without a degree that want to improve to be encouraged to do the same instead of being encouraged to read 3 wordpress tutos and start selling their skills by manipulating small business owners into spending money they don't have.
I trained developers with and without a CS degree and I always nudge them into improving engineering skills.
I think you mistook my A => B assumptions for a no B => no A which is a flawed logical reasoning.
You can have a degree or not, even bad developpers can hop from one job to another, making more and more money in the process, given they're good enough to manipulate the recruiters/clients into hiring them. Making money does not mean your product is good,useful or well-designed. It means you're a good salesman.
Congratulations, you're making money by manipulating someone into giving you their money. Awesome ! Thanks for playing, please leave.
I guess the point of the website is to encourage people without a CS degree to learn programming. That's great. The disctinction beetween CS graduates and non-graduates seems to be very unfruitful IMHO so encouraging people to pick up a computer is cool.
What I would sugget is to stop promoting sensationnal stories like the kid that is making 15k$ a month. This is purely manipulative and dishonest. This kind of journalism is plain wrong. Even if the number are true (which I highly doubt) encouraging kids to drop out of high school to study CS on their own is wrong. Getting a degree is the best chance you have to becoming good at it. You can still be creative this way.
More, maybe encouraging good engineering (or craftmanship whatever you want to call it) instead of instagram buzz and money would make tomorrow's software a little less frustrating to use and a little less bloated.
I would love to see a story, just once, with the title "this guy made a beautiful piece of software, and it's awesome"
I've litteraly never met any one praising OOP like this. Even if the intent of this introduction is to overly to make a point, I find it flawed.
> OOP attempts to model everything as a hierarchy of objects I never heard of anyone trying to use a hierarchy where it wasn't adapted
> The real world has no methods The real world needs to be modeled into something that can be computed by our human Mathematics. That's the whole point of modeling.
I'm waiting for the 'Functionnal Programming is wrong, let's go back to coding everyting in asm' post in 10 to 20 years
I guess that would be the age of smaller communities centerd around a few websites only? Maybe, I don't know if we can consider google as enabling a real global community as of today. I pretty much browse around the same websites. Anything I want to find without a precise source of information in mind, I use google and stumble upon ads and ads and sometimes ads, but rarely an answer.
I sometimes still search stuff manually browsing through websites indexes. Some things are difficult to find with keywords. Equations of which the name you forgot. Movies with a plot so generic billions of result would be associated with it on a search engine. That piece of music of which you could write the notes on a sheet but don't remember the title.
I don't think this question belittles Google's work.
I feel saying that would be like saying that animals that chose to live on the land were belittling millions of years of evolution in the water.
People working at Google chose to spends their time building a search engine for the world wide web, fine. That does not mean that sharing information accross a network has to be done via { world wide web, google }.
All of this is purely theroical of course, but I'm sure someone more creative than me would find another solution. Maybe not a solution that would exactly fit OP's description, maybe not a solution that would be practical with the current infrastructure.
But a solution that would render Google as-is obsolete ? Yes, I think that would be possible.
Maybe I'm reading too much into this and it's just semantics quibbling but maybe talking about computers is not talking about coding ? I've never met someone able to pass for a programmer when they are not. I've always felt just asking candidates to talk about their last or favorite project help catching a glimpse of how they think about software problems.
Little anectode : my brother is the first software engineer of the family
Father : "Son, what kind of computer should I get ?"
Son : "I don't know much about choosing computers"
Father : "Don't you write software for a living ?"
Son : "Yes, exactly"
The passion that this kind of topic seems to unleash looks like the consequence of a terrible fear a loosing control over an irreplaceable tool. But no tool is irreplaceable : if you can't/don't want to(for political reasons) use node, npm or even javascript just use something else.
That just it. I have no opinion about who makes money from what. At least, not in this thread.
If npm stops being the go-to solution, another one will take its place, naturaly adopted by the community, following the path of least resistance. Centralized or not. It does not really matter. What does matter is the code that's being downloaded. Modules dependencies management is an old problem, countless of tools have tackled.
Is the node and front projects architectures that dependent on npm ? It's a little coupled but not that coupled ? The dependency management still require a little brain power from dev teams, or does it really fully relie on the package managers ?
I would add one more rule "make sure your user has to perform at least 37 clicks before accessing your ad riddled article"
That's why I insisted on the difference beetween imprecise and incomplete.
> I do not mean complete. You can knowingly give an incomplete spec to the candidate to see what kind of questions he/she would ask to try and get the whole picture. (or if he/she goes head first into an unsolvable problem)
I feel that using wrong technical vocabulary in a question is not a sign of a interviewer trying to make the candidate ask questions. Maybe it's just me.
I am not against it at all. It opens the conversation to some technical aspects that can be very intersesting to talk about.
As a candidate I love getting technical in interviews because It allows me to see how my prospective manager thinks. If we have radically different ways of taking care of a technical problem it's a red flag for me.
In the same area, I like the "let's talk about your last project" question too.
So, I've had my share of technical interviews and here what I observed :
I am usually unable to produce good software when the specs I'm supposed to use are not precise enough. I don't mean not complete enough. I mean not precise enough.
Be it on the job or in interviews I seriously question the ability of some interviewers to produce good technical interview questions.
By good I mean precise, using the right vocabulary.
I do not mean complete. You can knowingly give an incomplete spec to the candidate to see what kind of questions he/she would ask to try and get the whole picture. (or if he/she goes head first into an unsolvable problem)
But the details that are given need to be explained in precise terms. Not in a shadowy weird dialect based on a model that only the interviewer understand.
I've had my share of technical interviews and most of my fail attempts at live coding were due to (my lack of skill but also) questions not precise enough or misusing technical terms (sometimes even not grammatically correct questions).
The latter usually make me feel awkward because I wonder if those interviewers simply lack the minimum intelligence to explain a simple feature with precise words.
Good engineers I have worked with always use precise words to describe precise concepts. Using wrong or imprecise vocabulary is proof of a lack of understanding of the job and/or a will to try and sound "smart" or "tech-savvy" to compensate for some kind of inferiority complex.
So maybe a good advice to interviewers would be : technical questions on interviews yes. But good technical questions.
2. I massage my back with a tennis ball. I use it against the floor or a wall to massage the points in my back where the pain irradiates from. I think chiropractor call those trigger points.
3. I walk. Walking/standing as much as I can during the day has helped me a lot. Sometimes after work I take a long walk. Moving, exercising, is part of the healing process. But stretching is not optionnal. Lack of stretching + exercise is a recipe for disaster : the symptoms can worsen.
-- The pain from sitting all day sucks hard. It's so frustrating.
I spend at leat 15mn every night lying on the floor doing those exercises while my SO looks at me, both concerned and amused (I reckon she's used to it now ^^).
I know it sucks to add yet another routine to our daily obligations, but this one is important. As important as brushing one's teeth I reckon. If you work in an office. It can save you a world of pain.
You can consult with a physiotherapist to get more detailed and custom-designed exercises.
Good luck
What kind of skills in particular would you recommend to work on and how does one go about improving said skills ?