25+ yr Java/JS dev
Linux novice - running Ubuntu (no windows/mac)

  • 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle





  • Stifle? No. Just pointing out how odd it is to say the democratic process isn’t democracy. If you don’t like the options, go win some local and state primaries. Put non-fascist crypto folks on the menu and see how they do in the general. Push the party left. No one did that and here we are.

    Decrying that this isn’t democracy when you’re not trying to participate is a fascinating take. But also reducing it all to crypto here - no matter what direction it takes you - that’s fucking weird.

    But no, me saying you’re wrong isn’t stifling. This is a discussion board. If you can’t handle discussion maybe post these thoughts on a blog.

    Edit: I love how you reposted to say what you had to say in an even more offensive way. Like you read what you wrote and decided you were coming across to kindly and needed to throw some ad hominem attacks and such in. Sure sign of a winning argument.







  • The way I’ve dealt with this before is reference the ticket number in the commit message. Now the only tickets you ever need to review are the ones relevant to the element in question, and only those creating or modifying that particular property, which should be evident in your commit log.

    You don’t specify a language but I’d assume that is the footer definition/html and any scripts or styles invoked by it.

    But once you have an answer, it would be wise to document it in confluence somewhere, even if it’s something like “Footer green per request from Director, Mr. Smith” or “Footer color: arbitrary, green to differentiate profile pages. Verify changes with Director.”

    How to organize the documentation so that it isn’t difficult to navigate is another difficult question that is more art than science - one which has never been satisfactorily solved anywhere I’ve worked once complexity reaches a certain point, but I leave that exercise to the reader.




  • I was going to make the point that there may not be an error, but because you tell it to give you one, it finds something. But that doesn’t explain VSCode, you’re right. Every once in a while an IDE is just wrong. I was going to suggest trying a different IDE which might give you a less cryptic message. I often times find bad brace errors to be a result of something much higher in the code.

    But again, not knowing PHP, I could only take a stab at answering why with the AI. I’ve tried many times to have an AI help me with these tasks. And sometimes it’s very good at them, but other times I can spend hours refining my query and arguing with it and never make any headway.


  • I can’t read PHP, so I can’t tell you where the syntax error is, but the AI is only responding in a way to complete the conversation. It has no ability to comprehend the code you’ve written, it just knows that conversations that start off the way yours did, probably ought to end with a complaint about that closing brace - particularly if you told it what VSCode was complaining about.

    This is one of the shortcomings of AI code assistants - they can’t think abstractly at all. So it’s ability to answer a troubleshooting question depends greatly on how many times the same question has been asked on StackOverflow and elsewhere.



  • It doesn’t really matter all that much. camelCase is to break up the long variable names and help people find the word breaks. Like imagine linespacing. That could be line spacing or lines pacing, and a little context would help you understand which (yeah this is a bit of a stretch)

    As long as it helps clarify, it doesn’t matter. That doesn’t mean it won’t bug me if I think someone has done it wrong, but it doesn’t really matter.