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
Search - "color schemes"
-
I think the weekly rants just exist because @dfox & @trogus got banned from stackoverflow and they still have questions.
When it comes to learning cutting edge tech... Go build already!
I found Rust intimidating.
I read the first few pages of the official book, got bored, gave up.
Few months later, decided to write a "simple" tool for generating pleasing Jetbrains IDE color schemes using Rust. I half-finished it by continuously looking up stuff, then got stuck at some ungoogleable compiler error.
Few months later I needed to build a microservice for work, and against better judgement gave Rust a try in the weekend. Ended up building an unrelated library instead, uploaded my first package to crates.io.
Got some people screaming at me that my Rust code sucked. Screamed back at them. After lots of screaming, I got some helpful PRs.
Eventually ended up building many services for work in Rust after all. With those services performing well under high load and having very few bugs, coworkers got interested. Started hiring Rust engineers, and educating interested PHP/JS devs.
Now I professionally write Rust code almost full-time.
Moral of the story:
Fuck books, use them for reference. Fuck Udemy (etc), unless you just want to 2x through it while pooping.
Learning is something you do by building a project, failing, building something else, falling again, building some more, sharing what you've made, fighting about what you've built with some entitled toxic nerds, abandoning half your projects and starting twelve new ones.
Reading code is better than reading documentation.
Listening to users of your library/product teaches you more than listening to keynote speakers at conferences.
Don't worry about failures, you don't need to deliver a working product for it to be a valuable experience.
Oh, and trying to teach OTHERS is an excellent method to discover gaps in your knowledge.
Just get your fucking hands dirty!12 -
Notepad++ is best. It take seconds to launch and provide color schemes for every language and its indentation is really good.12
-
I finally got around to ledding up my board. Its powered by an attiny board so i can upload new color schemes on the fly.2
-
Moral of the story: sometimes you've got to take a hit to be better off in the end.
A client asked me to design flyers for him, at first I was hesitant since this would be a stand alone design task instead of one incorporated with development.
He kept asking since he liked what I designed for my other clients (logos, etc..) So I finally said yes and we agreed to a final preview before he would pay me. I had asked him for color schemes, certain pictures, info, etc. but he told me it was completely up to me.
I finished the design, sent him the preview and he told me it was shit compared to my other work and that he didn't want it anymore 😅. I used to get mad as fuck every time this happened but now I don't even bother .
I know many people are going to say "You should have had him sign a contract, bla bla". I know, I know, but you can't let people sign a contract for every small thing, it completely depend on the situation and I prefer to know which of my lesser known clients are assholes so I can quit accepting tasks from them. This saves me much more time in the end. -
Question to people who use vim as their main editor:
I want to use vim as my main editor and I setup a color scheme. This only looked the way it should in gvim but looked weird in vim. I have read online that this is because of the limited color support of terminals.
So the question: do you use gvim or how do you handle color schemes in vim?4 -
Adobe's ExtendScript toolkit is abyssmal. I find posts from 2008 referring to issues that have not changed even in CC2017. Do you think they are small issues I'm bitching about? I'll list 2. First, the toolkit only colours "var, return, for, foreach" and a bit more keywords and the strings, of course you can set up color schemes but those are limited and not colouring stuff. The second issue is auto-complete, it rarely kicks in and suggestions have 0 connection to what are you doing and are always the same. It doesn't recognize anything of what are you doing.
Probably in 2008 you had to program with the manual near you like writing assembler, now there's an improvement in 2017, they got a window named object browser or something like that that actually is a summarised portable manual that could've been easily transformed in auto-complete suggestions.
Adobe writes about this and I quote: "a complete integrated development environment". Although I will not write much scripts in it, I need to write a big one and thought about extracting that object data and putting it in a more capable javascript editor. LO and Behold what I discovered, the ExtendScript Toolkit that's supposed to edit Extended javascript and save it as jsx or jsxbin is almost completely (it has some dlls too) built using around 100 jsx files. It's the equivalent of building a js IDE to edit js.
Sorry for formatting, I'm on mobile, I tried. -
fuck!
When your hard drive crashes, and the most annoying thing you forgot to save is the color/syntax theme on your favourite editor.
(I'm canadian... favourite, not favorite, shutup red squiggly)
fuck!
45 minutes scrolling between color schemes in sublme.. none of them seem right.
Maybe it's monokai? I think...
or was it oceanic
FUCk!
oh well at least it looks like I'm working.1 -
What are some cool plugins, color-schemes, whatever else for vim/nvim?
Current setup is nvim + Plug + YouCompleteMe + UltiSnips1 -
!rant
Hey folks, I need some tricks. I am currently a junior dev and struggle with starting side projects. I have some fancy ideas I'd love to work on. Problem is, I HATE UI design. I can't start working on an idea because I want them to look awesome. It is absolutely no problem to code the logic / backend, but the fucking design... I just hate it.
For example, I have some fancy ideas for an file manager that fits my needs. Haven't seen something yet like I imagine right now. I mainly code in C# (or Java) and I have to develop custom UI controls for it, align shitty controls, think about freaking color schemes,... I hate it. I simply hate it.
Do you also struggle with that? Any ideas how to overcome that?
Cheers!4 -
!rant
There are so many options to pimp my linux system. Is there any point in time, where I will be finished customizing/prettifying my linux? I highly doubt.
BTW.. what is the best way to backup the whole config? (color schemes, themes, gnome extensions)2