4 ms·
i haven't ever used or owned a 3d printer and this part >This quote, "With some tweaks to my G code and use of a nozzle that is more suited for higher resoluti
by baq 10y ago
i haven't ever used or owned a 3d printer and this part
>This quote, "With some tweaks to my G code and use of a nozzle that is more suited for higher resolution prints I am confident that I could produce a part that would be very close to the quality of the Stratasys produced part." really summed it up. It sums to "I can tweak my setup and get this part to be good enough relative to the expensive machine." and that is great. What is missing is it is every friggin' part.
is sooo true regardless of discipline.
/rant on
sure, you can make vim/emacs/sublime or macos/linux/windows behave just like you want, but you have to do this on every box you ever touch (disclaimer: i use vim). as i get older, the more i want my tools to just work, without tweaking for hours that requires deep knowledge about the system i'm customizing, to the point of willing to pay money to get the customizing part done for me. in this case, the $200k machine most likely isn't used by a single person who knows everything about its quirks, so it's all the more important for it to work correctly without tweaking, on the first try. i wish more software was like that.
/rant off
- drawnwren 10y agoThere are tools out there that address your specific complaint re: software repeatability. A combination of Ansible/Emacs/Git dot files can yield a consistent environment across machines. Howard Abrams has some great material on how he does this with Emacs (howardism.org).
- geerlingguy 10y agoWhy stop at your editor? Automate your entire workstation so every last config is identical across computers: https://github.com/geerlingguy/mac-dev-playbook https://github.com/geerlingguy/mac-dev-playbook
- paulryanrogers 10y agoBecause automation takes time. Typically more than just doing it manually every time you move boxes. And sometimes the steps take hours worth of bandwidth when sneaker-net would suffice.
- vinceguidry 10y agoI applaud the effort, but this is not the best way to save the few hours it takes me to get a new machine up and running that I have to take every year or so. What happens if your build script breaks? You have to work around it then troubleshoot the problem. Already there goes your time savings. I keep my dotfiles in a repo, that seems to be at the appropriate level of abstraction. Easy to set up, easy to add to, I can understand everything its doing, if it breaks I can localize the problem and fix it exactly where it's happening. Trying to expand the scope to include arbitrary package management? I don't think the tooling is there yet, that will make this sort of thing very painful. The dotfile convention has been brewing for decades. Trying this will inevitably force you to make compromises, and compromises defeat the whole point. The work it does is fundamentally equivalent to a package manager, and existing package managers haven't managed to get it done yet. If every Mac developer can be convinced to use a package manager, and every package manager can be scripted, (looking at you, Mac App Store) and every app with a modular architecture also either plugs into an existing system or implements its own package manager, then this becomes viable. But you still need a modular and easy-to-manage way to manage app configuration too. If you can get them all to use dotfiles, awesome. But they don't now. Right now, invariably you're reduced to a pile of hacky workarounds. Any automation will have been done at the wrong level and will break constantly. The last time I needed to set one of these up, I started to write down a checklist of things to do. I gave up after I realized that I was just pulling the checklist from memory, it already exists and writing it down wasn't going to do much good.
- TeMPOraL 10y agoSounds like your job involves making small amount of similar text manipulations on a large number of computers. Which is different than what the tools you mentioned were design for - i.e. for doing lots of different jobs on a small number of computers. As a dev, I use two computers +/- a few shells for most of my work. Little enough to manage configurations by hand. I'm more like a machine shop from GP's comment - machine shops do jobs to the same standards, but internally, each one is likely to be unique in its setup, tooling and process. What you're ranting about is lack of tools suited for the kind of job you do. My needs are different, so my complaints will be opposite - I'd like tools to be more like Emacs; capable of being molded and integrated to better fit any given job I have to perform.
- baq 10y agoactually it's not that bad - i've got 3 boxen that i use regularly and that's it. the problem is that those machines get EOLed every once in a while (say, 2-3 years) and each time i get a replacement i dread about some config setting that i set to solve a problem or whatever and then forget about it. it's a problem that happens often enough to be annoying but also seldom enough to not be worth automating, because software evolves, etc. i've got a few most important dotfiles on dropbox.