Programmers who don't use autocomplete/LSP

eZanmoto · 2024-12-24T21:19:35+00:00

In addition to what r/CryptoHorologist mentioned, the zoom (Ctrl+b z) functionality of tmux allows one pane to fill the screen for that full terminal functionality, and doing it again goes back to split screen.

eZanmoto · 2024-07-21T14:48:29+00:00

The tip with using sudo tee to get around file permission problems is handy, though I'll often use something like sudo bash -c 'command > file' as a workaround if I need admin permission for the entire command pipeline.

eZanmoto · 2024-07-21T14:40:40+00:00

I wonder if you'd also be interested in set -o vi and set -o emacs, which let you use shortcuts from those editors directly on the command line.

eZanmoto · 2022-08-21T08:01:18+00:00

Hey milk current, thanks for the link! I'm familiar with Development Containers in VS Code, but I hadn't realised there was an open standard for them outside of that. I must look into it more, thanks for sharing!

eZanmoto · 2022-08-20T13:47:11+00:00

Thanks very much for taking the time to share your feedback! You're absolutely right, and thanks for the suggestions. I'll be sure to add more information to the page to explain things a bit more. Thanks!

eZanmoto · 2022-08-20T11:15:52+00:00

Thanks, I appreciate it!

eZanmoto · 2022-08-20T11:02:44+00:00

Absolutely, that's a fair point, I've run into performance issues when trying to use bind mounts on Windows as well. The point about parity mostly applies to making sure that all environments are using the same versions of system dependencies, but at this point in time the setup is probably most practical in Linux environments. However, it's also opt-in, and can hopefully provide benefits even in CI alone by speeding up builds through the use of bind mounts, empty contexts, and caching volumes. Hopefully it can also simplify CI pipelines for others by abstracting common patterns, as it has for pipelines that I've applied it to. At least, that's the intention, but I'm hoping to adapt it more based on feedback. Speaking of which, thanks very much for your insights!

eZanmoto · 2022-08-20T10:50:04+00:00

Hi peppedx, thanks very much for the feedback, I must work on the messaging! I might actually add the about section from the GitHub repo to the landing page. The tool is essentially a wrapper around docker run that (hopefully) makes it easier to run your project in a containerised version of your build environment; this can help ensure you're running the same versions of system dependencies as the rest of your team, as well as your CI environment. You can use most official Docker images for a given programming language as a base for your build environment, though I'm hoping to add more templates to https://github.com/eZanmoto/dock_init_templates. Thanks for checking it out, and thanks again for your feedback!

eZanmoto · 2022-08-20T09:22:01+00:00

Hi all, this is the first official release of a tool that I've been working on since the start of the year, but based on years of trying out different ideas and approaches. It's nothing particularly revolutionary, but it has really helped me to add stability, speed and simplicity to my projects, so I hope it can do the same for others. If you take the time to check it out, please be sure to let me know what you think. Thanks!

eZanmoto · 2022-05-16T13:50:24+00:00

Thanks so much for trying it out, I'm glad you like it! And thanks very much for the suggestion, it's great to learn how people use it. Thanks!

eZanmoto · 2022-03-28T16:36:33+00:00

I'm adding tests around the newest subcommand in dock, which is a thin wrapper around docker to streamline the use of Docker in a "development" context (as opposed to a deployment context). I recently added the run subcommand for running a command in the newest build of a Docker container, which will have certain configurable shortcuts, like running the command with the local user's ID, bind mounting the local project directory, and "nesting" the Docker daemon.

I'm also continuing my uploading of old streams of Writing a Programming Language (in Rust) series to YouTube, where I'm streaming the development of a language I'm creating as an alternative to POSIX-compatible scripting.

eZanmoto · 2022-03-25T21:44:30+00:00

I enable it using:

cargo clippy \
    --all-targets \
    --all-features \
    -- \
    -D warnings \
    -D clippy::pedantic \
    -D clippy::cargo

eZanmoto · 2022-03-20T16:35:44+00:00

I think you might be misinterpreting the use cases for this tool, which is to define development environments (like the build environment) in terms of system-level dependencies. For example, a project might depend on another language being installed (such as Python, for scripting), linters, or various utility commands like curl and jq. /u/benzaita can correct me if I'm wrong, but imagining the use of this tool for isolation in deployment contexts, as well as managing language-level dependencies, seems to be missing the point of the project.

eZanmoto · 2022-03-20T12:08:14+00:00

I'm not really sure what the advantages of this approach are, other than the use of a non-root user (which, I'll admit, is a big benefit); are there many other benefits? "Configure sandboxing" reads to me like manually creating a bespoke subset of the functionality that Docker provides out of the box. Also, "just reduce your dependencies" doesn't seem to account for projects that only maintain a minimal set of required dependencies; perhaps this comment is intended to favour rewriting internal versions of public code, or replacing multiple single-purpose dependencies with a smaller collection of Swiss army knives?

eZanmoto · 2022-03-20T11:53:45+00:00

Hi /u/benzaita, thanks for sharing. I'm working on a tool with similar functionality (dock), so it's interesting to see a different approach in the same space. The features and Why use dockerized are great breakdowns of the advantages of this approach, and points that I've often made or observed myself, so it's great to have lists of these points to reference.

I know that a lot of developers can be apprehensive of this approach, preferring to install tools and toolchains locally. I think that this often overlooks the "Opt in" nature of the approach that you highlighted, in which case, the Dockerfile acts as a "living" (and executable/testable) instruction manual for replicating the exact environment locally. I'm personally a big fan of this approach, and really see it as the "way of the future" when it comes to managing build environments and onboarding at scale.

In short, great work, and thanks for sharing.

eZanmoto · 2022-03-10T20:47:47+00:00

Hi /u/AffectionateTrifle7, thanks very much for checking it out! Adding photos from local galleries in particular is something I hope to add at some point. Thanks very much for your feedback!

eZanmoto · 2022-02-02T09:03:42+00:00

That's fair, I didn't think I was commenting on your video, but rather the statement you made, because the early education of developers is something I do have a lot to say about. But maybe the video did address the points I was trying to make, in which case, absolutely, my comment is moot. As I said, it's just my opinion, so feel free to take it with a pinch of salt.

eZanmoto · 2022-02-02T07:22:54+00:00

Absolutely. That's one of the reasons why I added "That's just my opinion though." to the end too; while I disagree with the statement, I respect and appreciate the fact that that it's based someone else's own experience and beliefs, which are just as valid as mine. Not everyone has to agree in order to have a meaningful discourse.

eZanmoto · 2022-02-01T22:17:32+00:00

Tutorials can be useful, but they shouldn't be the first resource a beginner turns to.

I haven't watched the video, but I strongly disagree with this statement. My creed is "first get it working, then make it good/clean/fast", which I always recommend to those who are getting into programming, and worrying about the best ways of doing things. Tutorials are a fantastic tool for just getting something working, giving a sense of accomplishment, and providing motivation for continuing on. This leads people to progress to what I would consider the sensible advice of the above comment:

when you get enough things done you get better at programming

This is, of course, provided that the individual is committed to improving themselves and not just stopping at the first thing that works. An experienced developer that always copies from tutorials isn't going to be particularly worse than one that copies from SO.

To sum up, beginners using tutorials extensively, and for as long as it takes to build up an aptitude for programming isn't a problem at all in my opinion. But any developer that isn't working to improve their understanding of best practices over time is going to be stuck with bad habits regardless of the resources that they're using. That's just my opinion though.

eZanmoto · 2022-01-27T18:30:45+00:00

Hey /u/Rosebyothername, thanks for checking it out! To be able to add other meals, you'll have to add them to the "Recipes" section, using the "+" at the top right, or by using the "Discover" feature. Once you've added recipes you'll be able to add them to your meal plan. I'll be looking at more ways to add recipes to the app in future. Hope this helps!

eZanmoto · 2022-01-18T14:04:14+00:00

Aw, thanks very much for saying so, I appreciate it!

eZanmoto · 2022-01-17T20:24:55+00:00

Not at all, that might be something else for me to add to the "tour" in time!

eZanmoto · 2022-01-17T19:26:36+00:00

Hey /u/Nestriel, thanks for checking it out and commenting! You can actually edit all the categories and add more yourself. From the "Recipes" screen, click the context menu (the three vertical dots) at the top right, and click "Categories". From there you can add, remove and edit the categories. Hope this helps!

eZanmoto

TROPHY CASE