|
Did he/she master the trumpet? Sounds like she/he had gigs. Classical? Jazz?
|
|
|
|
|
He mastered it in college, did cruise ships, then Vegas. Huge downsizing in business because bean counters took over, etc...
|
|
|
|
|
diligent hands rule....
|
|
|
|
|
The quickest way to learn anything is to go all in. Doesn't matter if it's software or a new language. Devote all your time to it and 10,000 hours later you might know a thing or two.
Jeremy Falcon
|
|
|
|
|
When I'm learning a new "thing" nothing else exists until I nail it -I think I may be a tad autistic
In a closed society where everybody's guilty, the only crime is getting caught. In a world of thieves, the only final sin is stupidity. - Hunter S Thompson - RIP
|
|
|
|
|
pkfox wrote: I think I may be a tad autistic
Maybe... but people always want to label something that's not the norm... even though the norm will always produce mediocre results by it's very nature. I do the same. Methinks you're just focused.
Jeremy Falcon
|
|
|
|
|
I have a small project to do and do not have enough time
diligent hands rule....
|
|
|
|
|
About the software, I didn't know that one, thanks.
Last time I had to make 2D things I went for NanoCad, very similar to older versions of AutoCad that I had seen in college.
About the learning point... (I now speak about SketchUp, I learned parallel to working in 2D with NanoCad)
I started looking at the context help of each button, then I tried to make some things on my own with that small knowledge, once I found enough "fvck you" moments, I went to youtube and searched for a good content creator (took me a couple of days to find someone good), have a look to his way of doing things. Go back and start working on my own again.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Patience, diligence and practice. There are no shortcuts.
Having said that, some CAD packages are fairly intuitive, and others not. Of the ones I used in my day, Autocad was gruesome, possibly the worst software UI I have ever encountered. Daxcad (now defunct, I believe) and Silverscreen were a delight to use. I found Fastcad and several other light- to middleweight systems somewhere in between, neither particularly easy to use, nor particularly difficult.
Golden rule is RTFM and keep it handy!
|
|
|
|
|
knowing the actual domain is really useful when learning a new software.
if you want to learn to use a CAD software, knowing what CAD is and what is the terminology and how things are done helps.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
I struggled at first to learn Fusion 360 (my 6th or 7th CAD system?).
I found a great step by step tutorial on YouTube. I watch the video at double speed to get the gist of it, then follow along at home. After each step I stop the video and parrot the step. The devil is in the details!
It's pretty easy - watching the video I press space, alt-tab to F360, do the step, alt-tab back to YouTube, press space to play. Rinse and repeat.
This really helped me learn the important but sometimes tiny details required to get F360 to work.
|
|
|
|
|
at least in the United States
4/20/2024
backward is
4/20/2024
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
And a proper 2024-04-20 as per international standard?
|
|
|
|
|
Obviously it doesn't work, which is why I specified US.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
So I got to thinking... dangerous I know. But curious to know how many peeps unit test their code. IMO some arguments can be made for not doing BDD/functional testing, but unit testing is hard to say "that's a bad thing" for.
I know for me, I used to loathe the concept of unit testing. It was like just as boring and tedious as documentation (that nobody ever reads). That was right up until it saved my bacon a few times. Prior to that experience, I've only ever seen devs write crappy tests that were useless and thus considered it a feel-good exercise for a green checkmark. Didn't really think about the dev just being lousy at writing tests. Still don't do TDD though, but fo sho do unit tests after development.
Anyone here big into unit testing? Yay? Nay? Has cooties?
Jeremy Falcon
modified 20-Apr-24 12:19pm.
|
|
|
|
|
No I don't Unit Test but I QA to nth degree. I find that the kind of apps I write are not easy to Unit Test and the effort to learn and then to implement is not worth my time.
Maybe that's why it takes forever for me to release an app.
Definition of a burocrate; Delegate, Take Credit, shift blame.
PartsBin an Electronics Part Organizer - Release Version 1.3.1 JaxCoder.com
Latest Article: EventAggregator
|
|
|
|
|
Mike Hankey wrote: I QA to nth degree.
Tru dat. A dev should be the first step in QA. Like sometimes you gotta wonder... did you even run your code bro? 
Jeremy Falcon
|
|
|
|
|
I'm a one-man-shop so any QA hasta be done by moi. *PartsBin - An Elctronic Parts Organizer[^]
I also use the app so as I find bugs they get fixed quickly. Working on a new version now, so QA in progress. 
*Shameless plug
Definition of a burocrate; Delegate, Take Credit, shift blame.
PartsBin an Electronics Part Organizer - Release Version 1.3.1 JaxCoder.com
Latest Article: EventAggregator
|
|
|
|
|
Nice man. The app looks pretty cool.
Jeremy Falcon
|
|
|
|
|
Thanks for the kind words.
Definition of a burocrate; Delegate, Take Credit, shift blame.
PartsBin an Electronics Part Organizer - Release Version 1.3.1 JaxCoder.com
Latest Article: EventAggregator
|
|
|
|
|
I am a fan of unit testing. So much that I wrote my own framework that I described in an article here. However I don't believe in TDD (I also wrote about that in a short blog post).
I call my strategy "Test Assisted Design"(TAD). Sometimes I write tests while I develop a piece of code because it's easier to verify just a small part instead of waiting to the very end. Most of these tests get discarded when the project is finished as they don't make much sense for a finished product. Other times I write tests in response to a bug report and I want to reproduce the bug and investigate. I never found myself writing tests in advance of the code itself as I understand you should do with TDD.
Mircea
|
|
|
|
|
Mircea Neacsu wrote: I am a fan of unit testing. So much that I wrote my own framework that I described in an article here.
Noice. Same here. It's like the more you do it, the more you see the usefulness. Kinda like eating your veggies.
Mircea Neacsu wrote: Sometimes I write tests while I develop a piece of code because it's easier to verify just a small part instead of waiting to the very end.
Same. Although, I don't use Jest or a testing framework for the temp/intermediary stuff. In the JS/TS world, I'd just pop open a JSFiddle or use a Node immediate window to test stuff. If the code does that I think it will, it makes it way into the routine that I'll eventually unit test for real. Those will hang around though.
Mircea Neacsu wrote: Most of these tests get discarded when the project is finished as they don't make much sense for a finished product.
Just the temp ones though right? You still keep the non-temp ones? I know for me, probably the best non-obvious reason to keep the non-temp ones is being able to automate finding out when someone breaks your code.
Mircea Neacsu wrote: I never found myself writing tests in advance of the code itself as I understand you should do with TDD.
Same
Jeremy Falcon
modified 20-Apr-24 13:35pm.
|
|
|
|
|
Jeremy Falcon wrote: Just the temp ones though right? You still keep the non-temp ones?
Indeed; a lot of those are for corner/limit cases that would be hard to verify from outside.
Jeremy Falcon wrote: being able to automate finding out when someone breaks your code.
AKA regression testing. Conversation overheard at work: "if you touch my code again, I'll break your 🐘 hand!" 
Mircea
|
|
|
|
|
No, but I am a hobbyist so my opinion probably doesn’t count for much. I just have the feeling that if you unit test then you end up writing the code to the test.
Reminds me of years ago there was a bad code contest on another web site. The idea was to write a bad calculator app that had to pass a predefined test.
One of the entries was so bad that no mater what numbers were entered into the calculator, the output was exactly what the unit test expected. But if anything else was entered it did not work at all. But as far as the unit testing was concerned, the app worked perfectly.
Within you lies the power for good - Use it!
|
|
|
|
|
Sup sup PJ, long time no type.
PJ Arends wrote: I just have the feeling that if you unit test then you end up writing the code to the test.
100%. Unit testing is like an art just like programming itself. And you do end up writing some extra code to test, and it takes more time, but it's sooooooooo worth it. Especially in terms of automating reports on code breaking, etc. It's like this, you're gonna spend the time one way or another... time writing good tests or time trying to figure out some crazy bug you have no idea about. Not to say testing will eliminate that, but it sure does help weed out the silly ones.
PJ Arends wrote: But if anything else was entered it did not work at all. But as far as the unit testing was concerned, the app worked perfectly.
Fo sho. That's what turned me off of it for so long. No different than using a pointer ya know. A pointer can speed up your application. Can also give it a segfault. The coder in question just wasn't too skilled at writing tests most likely.
Jeremy Falcon
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
