Details
-
AboutSoftware Engineer/Reverse Engineer/SDET
-
SkillsPython, Java, Rust XML, Linux
-
LocationVirginia
-
Github
Joined devRant on 1/27/2017
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@SystemZ, it really is. I'm impressed with how natural the conversation was.
-
Ramadan Kareem!
-
Sixth, if the mods feel my single post is inappropriate, they can certainly remove it - I have no problem whatsoever with that, since I'm well aware of the forum rules. Have a nice day, and don't forget to rock some sweet pajamas tonight!
-
@letmecode
If you look through my post history, you'll see that I've never done anything like this, so there's one indication that I'm not spamming. Indication two should be the app caps at the very top of my post... If you see something that says, "NOT DEV RELATED", you certainly have the option to give my post a skip. Doesn't bother me in the slightest. Third, this post is infinitely more useful than the repeated meme reposts we see here every day. Fourth, despite the fact that I didn't mention it (because this post isn't about me) I AM actively coding an app related to Lupus, so there's my reasoning for sharing this post with the community. Fifth, I'm sorry that my single post - in this sea of development-related comments - triggered you SO much that you just had to jump in to downvote and comment... Sounds like a you problem though. -
@gloslistan I use comments in the same way - as headers for quick reference. I'm torn though... I like comments as long as they're to-the-point, but I also know people who abhor them. At work, they're a must, considering I'm not the only one working on the project (and our lead is remote), but in my personal projects, I keep them a little bit less verbose.
-
Ragnar Quackbrok
-
I'll go out on a limb and say he probably let the stress mess with his mind, since he was likely thinking of chown and chroot, but damn... Cron isn't easy to learn, and there's no shame in admitting you're not well-versed in its uses. 😕
-
Time to code myself an escape pod to Dagobah.
-
My best advice is to learn to unplug and relax... From October to the beginning of January, I was working on one single project all day, every day, and it burned me out. I decided to take a step back, spend time with my girlfriend and friends, and didn't touch a bit of real code again until last week. That time off allowed me to reset, unwind, and come back to work with a clear head, new vision, and renewed passion.
-
For what it's worth, I'm hearing great things about the NEW i7 Dell XPS 13. I've got a 4 year old Toshiba Satellite with a 3rd Gen i7 and (upgraded) 16GB of Corsair Vengeance RAM, and it runs like a dream. You may not need to spend a thousand dollars on a new machine... I got mine for $425 when it was brand new, and like I said, it's still going strong.
-
I had this "issue" too. I opted instead, to just access the podcasts in Google Music. There may be a logical reason for excluding the podcasts locally (app or database size, and maybe the lack of desire to build out a full music player interface are my thoughts).
-
@MajorRocki I think so too. It should give you the flexibility you're looking for, without having to literally build all of your packages from source. With Pacaur, Pamac, or Octopi (GUI package managers), maintaining an Arch system is pretty easy. I definitely recommend keeping an LTS kernel installed though, just in case you run into problems and need to roll back from a non-LTS version. Nothing is more frustrating than having to reinstall because of a kernel update that doesn't play nice with your hardware.
-
If you *really* want to build your distro from the ground up - and have the time to dedicate to building packages from source, and maintaining the system - then go with Gentoo. If you can't spare the amount of time that Gentoo will require, then go with Arch. You'll be able to build the system you want (from binary files instead of source packages), and you *can* get a pretty stable system of you stick with the LTS kernels and packages you're familiar with.
If neither of those will install, you can look into Manjaro (Arch-based), openSUSE (I recommend Tumbleweed), or even Solus (very exciting new built-from-scratch project with a *very* involved dev).
Personally, I'm biased towards Arch, as in familiar with it, and know that - with a bit of tweaking - it's a great daily driver. I've only ever played around with Gentoo on a friend's machine, but I've never tried installing it myself. -
The rest of the plunder!
-
I can't help but laugh... Then I stop and think about all the times I've had to run for the bus or train, and I realize that I'll probably do exactly this one day. 😂
-
@linuxxx, I've never actually used GitLab as I find it a bit redundant. Are there any discernable differences and benefits to using it versus Github? I'm always looking to add to my skill set.
-
I never even considered writing a script to automate repo creation. Great idea!
-
(100++)
How am I just discovering this now?! Great share, thank you! Seriously, this needs to be an intelliJ or Android Studio plug-in. -
Nice setup! I've been meaning to give i3 a serious shot myself (I'm naturally more of a DE person), but haven't had time the last few months. How are you liking the minimal environment so far?
-
@tytho, I completely agree. There's no substitute for knowledge and understanding.
It sucks that the senior dev quit, but I honestly hope he wasn't the only one who was headed out the door. Whoever allowed that junior dev to work on a live project, was out of their minds. Let him break stuff on a meaningless git cloned repo, not something that's in production. Absolute madness - madness I say! -
Gitkraken is great, honestly. I use the terminal for all of my commits and such, but for getting a quick overview, reviewing progress, and creating new branches, Gitkraken is my go-to. Terminal is easy enough, but having the GUI front-end makes project and workflow management much less stressful for me.
-
@Prans, I don't see why not. VM is a sandbox, so the Manjaro install shouldn't conflict with any of your Ubuntu stuff.
-
I really used to love Mint Cinnamon, primarily because it was better than Ubuntu proper, but also because I didn't have the comfort level to use Arch on a daily basis. Manjaro KDE pried me away from Mint though. It's better in every respect, and I couldn't be happier. To be fair, Manjaro got me away from Arch proper as well, since it offers the power and control of Arch, without the hassle of constant package maintenance.
I'm comfortable with Arch, but I don't have the time or inclination to fix code on my personal computer... I just want it to work. In my opinion, Manjaro is the perfect long-term distro. It does just enough hand-holding to make new Linux users comfortable, and offers enough power and control for advanced users. Honestly, my next step after Manjaro, will likely be Gentoo or even rolling my own distro, based on Arch. I really can't stress enough, just how impressed I've been with my Manjaro experience.
/2cents -
Lol
-
@vickylaixy, it could be that LightDM is loading before your graphics drivers (possible if you're having problems with your Nvidia card). It may require an edit in the lightdm.conf file.
-
@Prans, what distro are you switching from exactly? If you want something powerful and flexible, but don't want to go all the way to Arch, I'd suggest Manjaro.
-
I can relate to this. Dealt with a teammate who did exactly this, which made reviewing and fixing his code a nightmare. I ended up rewriting every class he was working on, from scratch. His response, "Haha, yeah, people have told me I'm difficult to work with."...
Me: 😒🖕 -
sudo pacman -R my-eyes
sudo rm -rf / -
@vickylaixy, which DM are you using? And which distro do you have running - Arch?
If so, there should be a section in the wiki regarding known issues with things like this. -
@veruz, I completely agree. I waited 4 months before I decided to root my OG Droid. I was so paranoid that I'd brick the phone that I did nothing but lurk on XDA and Droidforums, and read every article I could, so I could educate myself and get comfortable with the process. Obviously, four months is a pretty ridiculous amount of time, but during that time, I learned a lot and was better off for it.