Book — Coding for engineers — first chapters online #24
Replies: 8 comments 8 replies
-
While reading the Fundamentals chapter, I noticed how each new question I had was answered in the subsequent paragraphs. Many concepts that would typically be glossed over were elaborated on as they were introduced. I like how Lin expressed his opinions on certain conventions e.g. Variable naming styles. I also like that Lin is bringing his years of experience in teaching the subject, so consequently there is a certain confidence and security that comes with learning from him. |
Beta Was this translation helpful? Give feedback.
-
The next chapter is online. https://picogk.org/coding-for-engineers/3-running-code.html |
Beta Was this translation helpful? Give feedback.
-
Thank you for your work Lin! I believe in voxels too 🫡 Just a note. Unless the location of the zeros are as below on purpose (for learning debugging and troubleshooting) https://picogk.org/coding-for-engineers/4-classes.html `TeslaRoadster oFredsCar = new(0, "Fred's Tesla"); TeslaRoadster oEmmasCar = new(0, "Emma's fun scooter"); There might be a typo as the order has to be reversed for the values to be picked up: TeslaRoadster oEmmasCar = new("Emma's fun scooter", 0); ![]() ![]() |
Beta Was this translation helpful? Give feedback.
-
Hi All, Thank you again for taking on this task and helping me to learn something new. I am excited to start implementing these lessons and start making geometry soon. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Hello @LinKayser, thank you for all your efforts to educate the world on this paradigm shift of engineering. I have a question; I have been trying to understand what exactly are computational engineering models beyond the abstract notions that are so frequently mentioned in your articles and such. Are there plans to go over how to build our own CEMs in your coding for engineers series and perhaps releasing with it some solid example of a CEM? Also, as far as feedback. As someone who has been programming for over 10 years, I find your series on programming to be very clear and concise. It isn’t dense so it’s easy to understand the ideas and has served as a good review resource for me. thank you Mark |
Beta Was this translation helpful? Give feedback.
-
I do wish you luck. I find it...strange...that people don't code nearly as much as they do. For me, I came to Engineering from the other direction. I started by coding...then by learning the math associated with computing (I am a Computer Scientist by degree)...and then reached to Engineering. For me, coding comes...heh...naturally...as naturally as the Engineering does now. So...hopefully, you will show many the same journey I'm now on and have been for decades...which now takes a new and interesting turn with PicoGK. |
Beta Was this translation helpful? Give feedback.
-
Here's a post I just wrote on LinkedIn.
Please free to give me feedback here in this thread.
OK, I have just committed to teaching engineers how to code — wish me luck! Most engineers don't know how to write software. This is wrong. Coding teaches you computational thinking. Computational thinking is an important way to analyze and understand the world. To an engineer it is as essential as math. Period. But it is even more important for the emerging paradigm of Computational Engineering. As an engineer you should not have to engage in the manual labor of pressing buttons in a CAD program. You should encode your knowledge into computer algorithms, that are reusable and eventually do most of the work that currently consumes your life time. This elevates your skill and allows you create machines that have never been built before.
I wrote PicoGK, our #opensource kernel for Computational Engineering last year. Since then, people have asked me constantly about a good programming course to get started. I couldn't find one that I liked. So, I have embarked on this project, where I will write a book on the topic. By the end of it, you will know how to be a Computational Engineer using PicoGK ("peacock").
Not in a bare-bones simple way — but to really architect Computational Engineering Models, like we create at LEAP 71. This is not "scripting" or hacking together Python scripts. It's crafting object-oriented, engineering-centric, software to elevate the profession of engineering.
I am doing this the way I think it should be done, and it may be a bit unconventional. So, please give me feedback, I promise to incorporate it. I am doing this publicly on the LEAP 71 Github, which feeds into the PicoGK.org website.
I am planning to release one chapter a week (I hope I can keep it up).
I just put the first chapters online, check them out: https://picogk.org/coding-for-engineers/
Beta Was this translation helpful? Give feedback.
All reactions