UArizona Systems and Industrial Engineering’s Post

Does anyone know of an undergraduate program/bootcamp/accelerated online program for Computer Science or Software Engineering that's local to Southern NH? or completely virtual. I'm asking for a family member. #ISO #softwareengineeringschool #computerscience #acceleratedprograms #undergraduate

The 2024 University Ranking Report by CodeSignal evaluated a total of 50 software engineering programs in the United States based on the objective coding skills of their students, and Carnegie Mellon University tops the rankings. The rankings are derived from the results of CodeSignal’s General Coding Framework, which measures core programming and computer science fundamentals. This skills-based approach underscores the importance of evaluating skills to identify top talent and promote diversity in recruitment. Full report in comments.

It seems that this student is not interested in coding and was forced to take computer engineering. Answer to I've been admitted to a computer science engineering, but I'm unfamiliar with coding and my computer knowledge is limited to what I learned up to the 8th grade. I need guidance on where and how to begin my learning journey? by Sanjay Kumar https://lnkd.in/gPpjtrTs #students #engineering #embedkari

Tales from the software engineering trenches... This one exceeds the character limit for LinkedIn posts. But I cannot trim it further. Head over to my blog to read:

Bring your code and learn how to make it better during the 🆂🆄🅼🅼🅴🆁 🆂🅲🅷🅾🅾🅻 on 🆁🅴🆂🅴🅰🆁🅲🅷 🆂🅾🅵🆃🆆🅰🆁🅴 🅴🅽🅶🅸🅽🅴🅴🆁🅸🅽🅶! September 23 to 27, 2024 #RSEng #BetterSoftwareBetterResearch

SOFTWARE ENGINEERING 🌐 HISTORY OF THE INTERNET https://lnkd.in/d8JpyUYj #Software #Computer #Engineering #SoftwareEngineering #ComputerEngineering #Internet #History #InternetHistory #HistoryOfInternet #HistoryOfTheInternet

🌟 First Guest Lecture at Purdue University! 🌟 Today, I had the honor of giving my first guest lecture for ECE 461: Software Engineering at my alma mater, Purdue. A special thanks to Professor James (Jamie) Davis for this incredible opportunity! The topic of my lecture was "What College Won’t Teach You About the Software Engineering Industry", where I covered some industry insights that often aren’t emphasized in college: 💡 Leetcode doesn’t make you a software engineer – it prepares you for interviews, but real-world engineering is so much more. I don't know who needs to hear this but I wish someone had stressed this more for me when I was in school. I used to think that being good at competitive coding meant that I will breeze through my job. This couldn't be further from the truth. 💡 Learn to read other people’s code – in university, you are often times working individually or with a small team where you know everything about the code you are working with. In real life, you might have to work on a codebase with millions of lines of code, no documentation and the person who wrote the code probably resigned years ago. 💡 Learn how to debug – this is one of the most valuable skills you’ll use daily. Whether its using a debugger in your IDE or using log statements in observability tools. Learn how to get to the root cause of problems. 💡 Contribute to open source – it helps you learn and write high-quality code. You will likely work on a very well maintained codebase with some of the best developers. 💡 Be kind, be humble – In a cutthroat industry such as tech, a little bit of kindness goes a long way. This will help you way more than you think. I truly hope the students found value in the presentation, and I’m grateful for the chance to contribute. It was an amazing experience, and I look forward to more opportunities like this in the future! And please, use the comments section to add more points which you believe aren't stressed enough in college. #technology #computerscience #engineering #software

🌟 Empower Your Software Engineering Journey: A Path to Mastery 🌟 There are two types of software engineers: those who understand computer science well enough to do challenging, innovative work, and those who just get by because they’re familiar with a few high-level tools. Both call themselves software engineers, and both tend to earn similar salaries in their early careers. But Type 1 engineers progress toward more fulfilling and well-remunerated work over time, whether that’s valuable commercial work or breakthrough open-source projects, technical leadership, or high-quality individual contributions. Type 1 engineers find ways to learn computer science in depth, whether through conventional means or by relentlessly learning throughout their careers. Type 2 engineers typically stay at the surface, learning specific tools and technologies rather than their underlying foundations, only picking up new skills when the winds of technical fashion change. Currently, the number of people entering the industry is rapidly increasing, while the number of CS grads is relatively static. This oversupply of Type 2 engineers is starting to reduce their employment opportunities and keep them out of the industry’s more fulfilling work. Whether you’re striving to become a Type 1 engineer or simply looking for more job security, learning computer science is the only reliable path. If you want to become a software engineer, check the roadmap: https://lnkd.in/dv3dk6AN Content Source: https://lnkd.in/deVBVF23 #ComputerScience #CareerDevelopment #TechInnovation #AIRevolution

Real-world software engineering versus academic computer science theory. Blend it or leave it? 👀🤔 We vote for the holistic approach! Read about the foundations of programming rarely covered in university classrooms. 👨🏫

The last post about simplicity vs abstraction was a comment on the recent debate taking place on whether a course or a set of courses - of four months period - is sufficient to make an individual market-ready for software engineering and / or development role. There's a always a difference between knowing the path and walking on it, superficial knowledge about tools and programming languages will never be enough for a person to take on real-world challenges. Fundamentals and basics provide more depth to your understanding in a way that makes you more resourceful in finding better solutions for the problems you'd face - where other with shallower knowledge and experience would find impossible to tackle. And to gain such power you have to practice long enough, face more diverse challenges and, work on achieving different kinds of requirements. In conclusion, studying gives you knowledge while practicing gives you experience, you need these two rails to guide you through your career and, that requires a great deal of time.