hatsubai
I'm finding I need to commit and print a lot of these. Logic's little checker in the upper right showing RAM, Disk IO, CPU, etc also show that it is getting close to memory limits on certain instruments with many layers.
So as someone who would be willing to dump $4k into a laptop where its main workload is only audio production, I would feel much safer going with 64GB knowing there's no real upgrade if I were to go with the 32GB model outside of buying a totally new machine.
Edit: And yes, there is does show the typical "fear of committing" issue that plagues all of us people making music. It's more of a "nice to have" than a necessity, but I would still consider it a wise investment. At least in my eyes. Everyone's workflow varies and others have different opinions on the matter.
It has since healed, and I am better now. However, there was a point in time where I had to continue going to the gym and keep using those weight machines. It took a few years before I was back to normal and could start working with more generalized equipment. So there's more than just a sports-focused need (like MMA fighting or football) for gym equipment, and that equipment cannot easily be substituted, nor can it be done safely with a bike or a heavy stone.
Most houses I have lived in, and the houses my peers owned, were all one story houses. Those who lived in what insurances labels as "known flood zone" areas still had carpet, and the houses are decorated no differently than the houses I have seen in California when I lived there, as well as Michigan where I currently live.
We also were able to enroll in flood insurance without any issues. Granted, it's extra insurance on top of typical home owners insurance, but Allstate had no issues providing us with flood insurance for over two decades of living there.
Is this perhaps how the more wealthy people live, or is this maybe how a specific area lives? I have legitimately never heard of people purposely furnishing their first floor as if it were a basement. I have seen the trend of moving away from carpet, but that is a more general trend that I am observing here in MI, as well, so I am not entirely sure it is can be directly linked to home owners worrying about potential flooding.
Given how context-heavy Japanese is, it was nearly impossible to translate exactly what was going on as the Google Sheets only contained the additional content and not the full game script. Even if I did have the game script, there are still certain contextual things which are only realized when seeing what was happening to the characters on the screen.
I ended up watching an entire "Let's Play" of the series in order to get the gist of the story, get the character names correct, and see how the original translators localized everything. I took cues from their localization and did the best take I could at the time in order to translate it while balancing heavy workloads at school.
I'm both somewhat proud of the translation and somewhat disappointed in it. I feel as if I could do a much better job if I had more free time to update it, but localization is kinda like an art. Very few people will translate the same content the same way - even the same person might translate the same lines differently at different points in time.
I do something completely different these days and don't get to utilize my Japanese nearly as much, but I'd definitely be up for another game translation again. While you may be bound by certain external forces (pre-localized content you need to mesh with, author's wishes, censorship, etc), there is still a lot of freedom and liberty in localizing. After all, it's your job to retell this story as best you can to your target audience, and it requires both knowing the source material's culture, as well as your own. In fact, it probably requires knowing your target culture even more so, and it's this type of creative challenge that really got me excited back in the day.
Right now, we are looking at moving away from vxWorks and onto a Yocto-built Linux with the RT patches to the scheduler. From a requirements standpoint, the RT patches meet our needs for "real time" since our timings require more of a soft real time than a hard one. There's also way more support out there for Linux, and I am also slightly biased in that I am more of a Linux guy than a vxWorks guy simply due to familiarity and ease of troubleshooting.
This latest news with vxWorks is great, however. I actually sent this to management because we are attempting to figure out what direction to take as our current version is reaching EOL.
It provides extremely detailed information about everything going on in Linux, as well as example programs and exercises to help you further your knowledge. While it doesn't get deep into kernel theory like Tanenbaum's books tend to do, it will provide you with a greater understanding of how things work, IMO.
* If there are any issues at all, he is always available to listen. I am free to contact him at all hours during any time of the day, and he'll respond as soon as he can. In turn, I do the same for him. If there's ever any issue, I immediately jump on it and prioritize it, if possible. One thing to note is that I get 1.5x pay for every hour I work extra, so I don't mind spending a few extra hours to try to help out late at night if need be. It should also be noted he's only ever asked me to help work late once during the nearly five years I have been here...and I got a huge paycheck thanks to it.
* He keeps me out of unnecessary meetings and makes sure I only attend the ones that need to be attended. He attends the various program meetings and other leads meetings so that I can focus on actually programming. I have maybe one meeting a week thanks to this despite co-leading the BSP dev team here on at least four different programs.
* He listens to me when I suggest stuff and takes what I say seriously. I am free to speak my mind without consequence, even if it's questioning his decisions or direction. As such, I respect that he can override what I say and will go along with his final decision. That said, usually whenever I bring up something critical, he jumps right on it and begins talking to higher ups ASAP regarding how we can solve it.
* He gives actual feedback. If we, as a team, drop the ball, then he'll make sure to point that out. If we, as a team, do well, he'll make sure to mention that. If you perform well, he will make sure you get recognition from higher ups.
I now work in a completely different part of tech (from web/mobile SPA dev to embedded dev doing defense work) and make more than I was making in the Bay Area. I live relatively comfortably in a gated community, but I honestly cannot stand the weather here. It is so bad that it is affecting me mentally to the point where I think I have mild Seasonal Affective Disorder. The Bay Area had some financial hardships, but the weather was nice, and I wasn't dreading six months out of the year like I am living here. I was healthier there thanks to always jogging outside in the awesome weather, the scenery was better, the roads were better, the food was nicer, there was more intermixing of different cultures and values... I'm looking to head back to the west coast, or maybe even the southwest, but family reasons are keeping me here for the time being and preventing me from moving.
You didn't really list why you're asking this question. If it's purely monetary-based, sure, you can possibly do better elsewhere. However, I have found that it easily has a hard salary cap real quick. I haven't come across many people who make more than $160k all in after they worked 20+ years in the industry, and the area I live in pays higher than other Midwest areas. Housing prices are quickly getting into the $400k+ for nice houses, and the price of a lot of goods is very similar I have found (most big purchases like laptops, cars, TVs, etc are the same whether you're in CA or in the Midwest. The main difference is the tax. I actually pay more for car insurance here than back in the Bay Area). Utilities are basically the same, it seems, so that didn't go down. Internet price is the same, too, and those cost of living calculators don't always tell the whole story. It's just some stuff to keep in mind if you plan on moving for solely monetary reasons.
I eventually moved on and now have a cubical. I find myself able to be much more productive than ever before. Part of it is because I don't feel like someone is staring at my back and checking my monitor all the time. Another part is that it is vastly quieter than the previous work place despite having literally 100x what the last place had (from startup to Fortune 100 company). If I want to communicate or collaborate with others, I can hit them up at their cubes, and there can be little group discussions in the hallways between cubes without being major distractions to others. I don't get the insane ear fatigue I'd get with headphones in 6+ hours a day like before, too. Needless to say, based on my experiences, I personally prefer cubes to an OO layout.
As far as actual FB usage is concerned, I use it maybe once a year to post something - if that. I rarely even use Messenger outside of the aforementioned groups aspect (communication for buying/selling, mainly). If friends or family need to contact me for anything meaningful, I have other mediums I use.
Remote: Sure
Willing to relocate: Sure
Technologies: C, C++, Python, Bash, Git, Linux, vxWorks, Yocto, Buildroot
Résumé/CV: http://thomasice.com
GitHub: https://github.com/tomice
Email: [email protected]
About: 4+ year embedded/Linux BSP/OS developer at one of the world's largest land systems defense companies working mainly on x86 architecture. I'm always open to new opportunities and interesting ideas.
That out of the way, don't give up. There are lots of positions out there, and many people are hiring. Keep on trying and don't give up. Careerbuilder and other websites can help a good bit in terms of getting your name out there. Recruiters on there and other resume places have helped me find other jobs, and I am currently at a solid company with good pay. Passion helps a ton, I've found. Find something to be passionate about, both in the tech field and outside the tech field.
But just to touch one more thing - the concepts you are struggling with take practice. I had to teach myself most CS concepts, and a lot of it involved going to MIT's site or going to Harvard's site and grinding them out. I spent many many hours on YouTube and elsewhere just trying to understand the concepts and, most importantly, writing software utilizing these concepts. I still regularly quiz myself once a month on some random interview question, such as how to write a DFS or BFS from scratch, how to reverse a binary tree, or how to implement something like Dijkstra's from scratch without looking anything up. If I find myself needing to look stuff up, I make a mental note on the concept(s) I'm rusty on and do a few more exercises pertaining to the concept. If I find the stuff easy, I make sure not to review it for quite awhile (utilizing Anki is a great way to do this, by the way).
It's a solid career choice, especially if you want to branch out into automotive where they are hitting this field hard. The skills you learn are also applicable to pretty much anywhere where you use Linux, so the transferable skill set overlaps a good deal.
There's a really good book I recommend that describes basically anything and everything you need to know called "Mastering Embedded Linux Programming" by Chris Simmonds. It'll teach you pretty much everything you need to know to get up and running in the embedded Linux world. It's also a ton of fun if you've never messed with something like a BeagleBone.
That said, I'm looking to get out of the defense industry and getting back into app development. Part of it is because I want to work with newer, more exciting technology. I'm looking towards possibly going back to mobile development, even. Unsure at the moment... Keep in mind that this has nothing to do with the stability of the market. I honestly feel it's way more stable than most people seem to give it credit for, especially the embedded Linux side of things.