Who doesn't debug on the toilet? Some of my best ideas happen in the bathroom!

Im down for the laptop battery and the bugs, pass on the rest ha.

The great thing about this is any company pulling that DB for marketing purposes is likely to not protect against SQL injection from a cronjob

Just need to set width on that text block and add ellipsis to true. It looks like their backend is adding the ellipsis, so they'd need to change that. All in all, a day of work. I bet.

@Alice can always count on your comments to fix bugs.

Honestly though, there is a way to compartmentalize. You can indeed time box and pivot and change tactics in a way that prevents you from falling into a major time suck. My complaint is when folks can't figure out how to do that and they only have 1 mode of operation. The right way to do things is BS, it doesn't exist, it's a fucking illusion. Pragmaticism above all else.

@CurseMeSlowly you know, that's a pretty good perspective actually. I don't necessarily like the outcome but at least I know what I can expect and who I can count on.

It's fairly safe to not support anything but IE11 these days anyways.

Un-fun tangentially problem - Chrome localizes error messages so consolidating them in something like sentry is near impossible.

@Aitkotw if I cut my hair I won't be able to code anymore

I'd avoid windows for web dev. Node mostly works on windows, but since most of the web is hosted on Linux you may find basic compatibility issues for some packages. Osx or Ubuntu are probably your best bets in terms of ease of use and compatibility.

At minimum you may find docs for how to set up things on windows to be sparse.

@atroxi hah, ya I kept revising my comment as I found more things wrong with it.

My 2 cents - I've worked in code bases that were complete dumpster fires in terms of structure. Every now and then, someone would try to start a project to move all the code. Basically it just made things worse. No one ever finishes everything completely in a large code base.

Honestly that structure is far from the worst thing I've seen. It's main problem appears to be the synonyms. What's a module vs a component? Plugins vs vendors? Base vs layout? I don't mind the numbering, except for the obvious missing no.

Oh maybe it is kinda of a bad structure ha.

@elazar if you are looking at the characteristics of a data structure without needing to know it's implementation the only characteristics that matter are its apis and performance. It is why you can safely use objects as hash maps in JS. The performance characteristics and APIs are such that they resemble hashmaps and that's all that matters. It is also why arrays in JS can be treated as stacks, queues, arrays and linked lists.

I guess I'm saying the performance characteristics describe the data structure equivalently to the API it provides.

The difference is, when something goes wrong with a program in osx and Linux it generally doesn't crash the computer. I know windows has changed a lot, but this used to happen all the time.

@Triskelion I'm ok with all those concepts. +1 on all that. It's basically when people want to go beyond that and restrict functionality or force ordering of rules or whatever other rule. I'm also ok with code reuse when it makes sense. Example: use the grid when it makes sense, but not when it doesn't.

I've been shwifty my whole life

@vadimir sorry, I meant, the array implementation that most people end up using. I've very rarely used an array that didn't change in size... Maybe if delivered from a server side payload or something.

Note - careful, if you don't actually try to teach junior devs they often sink instead of swim. I highly recommend giving them books to read, giving them presentations and other formal training. Not everyone has the motivation to spend tons of hours in their off time learning stuff. Or at minimum, you may need to motivate that by illustrating that's how the world works.

This is every convo between QA and Dev

To be fair from a classical definition perspective. The array in JS works like an arraylist. if you analyze it's performance characteristics you get O(1) index look ups. O(1) additions. Slicing and all those operations are easy with lists, but harder with arrays. Also, standard arrays suffer from resizing every now and then. Can you imagine if almost every page had a "stop the world" gotta resize this fucking array issue.

Depends on some really bad logic on the backend. I suspect you'll get emails.

I had seen a bug at a company where people were using the password field as a DDoS mechanism. Since unlimited length PW were allowed, people were uploading files to spam the server. And doing this with just a few hundred bots was completely feesible.

That being said, 64 characters is probably still reasonable. 32... Maybe... Ehhh. 64 seems safer.

@nikolatesla (eng manager here) at first it sounded like a technical disagreement, but actually it sounds like there is just one problem, or just one main problem and that's the relationship with HR. It sounds like they are mischaracterising disagreements? Or technical decisions?

@Ashkin not arguing for or against those features. I'm just saying that those features don't define language or not language. All a language needs to be is a set of instructions that a computer can process. Some systems benefit from constraint and certainly CSS and HTML cause loops and branching to occur in browsers.

I'm fairly sure turning completeness need not be what defines a programming language. Domain specific languages, like HTML don't require Turing completness. The most generic definition of a programming language is "a set of instructions for a computer."

@inukinator css does have "calc", which isnt js. Not sure if the makes it Turing complete.

The cake is a lie, it masks systemic problems. Run now!!!

==, >= and =< cause type coercision. This is why JS the good parts and all books on JavaScript say you should use === of course you're out of luck for >= and <=. It would cause quite ambiguous behavior.

Coming from a developer who is really good at JavaScript... I think you should start with Python :)