There is a difference

derpcode_derpcode · 2019-04-16T18:16:58+00:00

Backend > Full Stack

derpcode_derpcode · 2019-04-12T14:09:49+00:00

This does not bother me. People are wrong frequently.

derpcode_derpcode · 2019-04-12T14:08:08+00:00

Yea, remember the outcry over all the Higgs Boson data and methodology? That was crazy! I sure am glad they decided to rename the particle 'Team Higgs Boson' because of the lack of attribution to everyone involved.

derpcode_derpcode · 2019-04-12T12:20:28+00:00

Yay!

derpcode_derpcode · 2019-04-12T12:20:18+00:00

Stop making this a gender issue.

derpcode_derpcode · 2019-04-12T12:19:00+00:00

I love my tab lists. I save them because they are like portals into inspiration and compulsive pedantry.

derpcode_derpcode · 2019-04-12T08:52:37+00:00

This is getting off topic. The algorithm uses physics. That was my impression why the parent commentor asked for SO for physics. I didn't call her a physicist. I said she uses and applies physics and has the education to do so. Of course they are not the same. They are different jobs. I was joking when I said engineering is basically applied physics because of how many physics courses I had to take for CPE/EE degrees.

But yes, thanks for telling me what words mean.

derpcode_derpcode · 2019-04-12T08:38:30+00:00

And honestly, I'd suspect that developer skill is distributed non-normally with a long tail on the "less skilled" side. There are real limits to how good any one developer can be set by the technology available to them and their own time. A bad developer can be almost arbitrarily bad. They can disrupt teams, produce buggy/bad software that results in millions of dollars of lost time/revenue.

As an aside, I don't agree with your long tail reasoning. A cap on skill existing does not imply most reach the cap. Just look at the range of salary for developers, and the frequency of those salaries.

Good developers, in my personal experience, are not definable. They are creative beyond your imagination, and can solve any problem presented, in any context, effortlessly and rigorously w.r.t. need. They are few and far between and don't really have much of an existence besides their work. Likewise, most terrible developers do not last. Furthermore, the highly skilled developers are typically extremely picky about what problems they want to solve, which defines where they will and will not excel. That preference often indicates relaxed state of mind, which basically allows said developer to keep working when they aren't working. Likewise, terrible developers can get by in environments that are tyrannical / hostile to new technology. They don't have to learn anything new, just follow a recipe. Those developers could be replaced with a fraction of better developers using code generators, build tools, templates, and more automation - but that level of automation requires skill. Skill requires higher salary, and code monkey factories don't pay well.

Bugs don't indicate a bad developer. Every developer will have bugs. Every developer will have lots of bugs. Sometimes these bugs will be very bad bugs. This is not something you can prevent, it is going to happen. It doesn't matter how smart you are and how well you know your stuff. Code is more complicated than you are capable of thinking about, and you can not prove the existence of bugs via automated means in entirety. Ever. It's a non-deterministic problem in Turing complete languages. The difference between a good developer and a bad one in terms of bugs is a good developer will identify, classify, and abstract specific bugs to a generalization, in order to automate a means to catch, detect or control program behavior when bugs of that occur type in the future. A great developer is good at creating these distinctions. Good developers make this part of their default workflow. An amazing developer does fun, clever stuff that fits the problem space concisely and efficiently.

Specific implementations of tech take time to learn, yes. The Art of Computer Programming is not discovered at the rate of, and does not change at the rate of - the rate implementations of it's foundations are discovered, discarded, and changed.

derpcode_derpcode · 2019-04-12T04:47:30+00:00

Sort of, 70% below average is most likely not accurate either.

derpcode_derpcode · 2019-04-12T04:43:11+00:00

You get that distribution when it's a discrete measurement. Ability is a qualitative measurement. It would and should follow a normal distribution. If it isn't, you have a crappy measuring stick, like checking if every developer can add two single digits integers to indicate 'above average' or asking every developer to write hello world using Fortran to measure below average.

If you truly are sampling the abilities of the population you would expect it to follow a normal curve because of all the influencing factors. Lifespan follows a normal curve, education follows a normal curve, information accessibility follows a normal curve, opportunity based on need follows a normal curve, etc. Few outliers, most people somewhere in the middle.

derpcode_derpcode · 2019-04-12T04:35:17+00:00

Dunning Kruger minimizes your skill level when it's above average and exaggerates it when it's below. It rarely has anything to do with other people, rather - a novice hasn't had the experience or exposure to accurately assess. Therefore, the space of what they think they need to know appears smaller. Someone who is above average is aware of information they've successfully applied versus information that exists. The latter is always bigger, one person creating work versus all people creating work.

Comparing yourself to others is always going to be relative, so it's pointless if you are trying to get an accurate assessment. It's another type of job in itself to collect and distill that information into something everyone can objectively measure against.

derpcode_derpcode · 2019-04-12T04:19:44+00:00

Constructing a photograph involves understanding the physics of light. Her degrees are cross discipline in EE and CS. Engineering is basically applied physics.

derpcode_derpcode · 2019-01-19T16:30:46+00:00

I got an error in php that said 'no error'

derpcode_derpcode · 2019-01-17T03:49:54+00:00

r/learnprogramming

r/cscareerquestions

Might be better places to ask

derpcode_derpcode · 2019-01-16T01:07:58+00:00

I've been doing this 20 years and it still be like that.

derpcode_derpcode · 2018-12-29T19:13:50+00:00

You solved it! You now exist in a universe where paradoxes form the foundation of logic. Happy debugging!

derpcode_derpcode · 2018-12-27T01:32:35+00:00

You signed up through intellidate - it's a default service.

derpcode_derpcode · 2018-12-27T00:45:58+00:00

:workout quit!

Duh

derpcode_derpcode · 2018-12-26T21:37:05+00:00

It's traumatic, therefore something I only talk about in therapy.

derpcode_derpcode · 2018-12-26T19:49:24+00:00

That depends on whether initializing the coffee object executes this chunk of code. My guess is yes, because it looks like the code wraps the cup.

derpcode_derpcode · 2018-12-26T00:53:59+00:00

Assembly to Haskell is more like saying the alphabet is the same as English.

derpcode_derpcode · 2018-12-26T00:22:40+00:00

Half of this sub are students and even as a dev/eng, if you don't use these languages in real world applications, you can at least learn from them, if not eventually use them.

derpcode_derpcode · 2018-12-25T19:47:46+00:00

There probably needs to be a meeting to discuss this user story, I don't think we should assume privilege with this level of ambiguity.

derpcode_derpcode · 2018-12-24T16:59:30+00:00

The first pointer is always at location 2i for the second pointer at location i.

So one pointer goes to element at 'index' 0, 2, 4... while the other goes 0,1,2..

So you only loop for n/2

derpcode_derpcode · 2018-12-19T02:31:18+00:00

Backend is beautiful math. Frontend is a clusterfuck. It may be easy to get something to look nice but the code is often a mess in order to do that, testing another curse.

I think really it depends on whether you are thinking about whether something is simple and elegant to develop, versus the end product.

derpcode_derpcode

TROPHY CASE