For context I have a few years of work experience primarily in Java and Python, but have also worked with a smattering of other languages professionally. I’ve also worked with a few proprietary languages with limited documentation and it was fine. At my current position I’ve been tasked with updating, maintaining, and supporting a large pot of Matlab spaghetti and I’ve never been so overwhelmed. I can’t really untangle whether it’s just poorly written Matlab or if large Matlab applications just should not exist. It’s gotten to the point that I’ve had Tetris-effect style nightmares of trying to keep all the nested struct arrays in my head. It’s drained all the joy I used to get out of programming, and it’s pushing me out the door. Has anyone else had to work with large Matlab applications and if so is this just par for the course or my own little ring of hell? All Matlab hate welcome
TC 🥜
Want to see the real deal?
More inside scoop? View in App
More inside scoop? View in App
blind
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
FOLLOWING
Industries
Job Groups
- Software Engineering
- Product Management
- Information Technology
- Data Science & Analytics
- Management Consulting
- Hardware Engineering
- Design
- Sales
- Security
- Investment Banking & Sell Side
- Marketing
- Private Equity & Buy Side
- Corporate Finance
- Supply Chain
- Business Development
- Human Resources
- Operations
- Legal
- Admin
- Customer Service
- Communications
Return to Office
Work From Home
COVID-19
Layoffs
Investments & Money
Work Visa
Housing
Referrals
Job Openings
Startups
Office Life
Mental Health
HR Issues
Blockchain & Crypto
Fitness & Nutrition
Travel
Health Care & Insurance
Tax
Hobbies & Entertainment
Working Parents
Food & Dining
IPO
Side Jobs
Show more
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
comments
There are a few 3rd party things to make life better (linter/auto-reformatter/auto documentation) but it is painful supporting matlab projects
Edit: One trick, if this doesn't need to be optimized, is that tables have more quality of life friendly syntactic sugar compared to arrays. If it's not in the actual computational part of the code, taking the performance hit can help your sanity. Also, pre-configure parallel code to pass data in and out and set up the parpool options; yolo'ing with parfor lead to more headaches than it avoided for me. For math, using the built in vectorization instead of any explicit parfor stuff is much better; I/O sometimes doesn't have an easy built-in parallel option though.