• 0 Posts
  • 14 Comments
Joined 6 months ago
cake
Cake day: March 6th, 2024

help-circle

  • We had the same idea. Even ended up living on an old 37’ for about a year… then we popped the stern tube during an engine test (40 years worth of copper corrosion)…

    Well you can imagine what that was like. It was only through sheer dumb luck that we saved literally everything we own. That coupled with some expensive engine repair and we ended up spending the cost of the boat again in repairs.

    There’s more to the story but ye, we live in a house now.

    This is not to discourage any one btw, just pick your boat better than we did. Also, you need to be really into DIY or really rich, because God damn, boat stuff is expensive!









  • Yes and no. I agree that camel vs snake or that stupid mNameThing that was popular for a while, doesn’t reeeeeaaally matter, although I would argue that convention over the language still has value. As an example, naming a Java variable with a capital letter would be confusing and annoying to any new devs joining the project, even if it’s a valid identifier. Also it’s handy to be able to look at something in ALL_CAPS and know that it’s probably a static final, without having to check it’s definition. I guess it’s about finding that line between useful conventions and pedantry.


  • Dear god please no. This way madness lies. Your idea of “whatever you think works best” is not going to line up with whatever the next person that comes along thinks, and your codebase is about to get all kinds of fucked up.

    Thinking code complete is going to save you is naive. Even in languages like C and Java, where it works best, you still need to be able to read and understand the code in context. There’s no hope in a language like Ruby with all it’s meta programming stuff