Details
-
LocationTokyo
Joined devRant on 7/10/2020
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
-
@AleCx04 btw in your version you can pass __func__ and some other macros to automatically get the function or the line number where the log statement was called
it's easy and maybe interesting for your case -
@AleCx04 C is very easy actually i think it's the best language and we've been going down the wrong path ever since
but yeah i don't really like the variable argument length syntax thing, I ended up with this
log_append("Variable i is currently: ");
log_append_uint32(i);
instead of
printf("variable i is currently: %u", i);
for me it's fine and i can focus on something else -
I have a logger in my c project and tried this to match the printf syntax but quickly gave up, dont get how those arg lists work
-
it's kind of difficult to judge without knowing what the thing is and why it takes so long to fix. Maybe delete and rewrite from scratch is an option?
-
Tell them you'll do it if you get a 20% raise
-
@nebula yeah man absolutely! I actually used Xamarin before to make my simpler apps because I was more familiar with C# back then. In the end I've come to the conclusion that writing everything in C or C++ and then having a small native layer of code (the minimum that's necessary) must be the best way to do it. I really think the tech community is kind of going in the wrong direction and so I like the old programming languages better but that's just me.
For Swift this really worked well and I didn't have much trouble learning how to do basic things. I didn't really have to invest any time learning swift properly. For Android Java so far I haven't found my groove yet but we'll see... -
@nebula Thanks! Had no idea about this. I dislike IDE's and build tools in general... I spent a bunch of time yesterday and am set up to iterate quickly from the command line now... I tried to get away from gradle as well but holy shit that seems impossible there were just 5 more build tools underneath and some deprecated tools wtf :/
I tried pretty diligently to have a small Swift platform layer so I think I'll try to copy that in java instead of going to native c++ for now... (watch me give up in a week)
I think I'll code in vim and switch to android studio for debugging whenI get stuck or need to download emulators/sign apk's -
In general people have really shifted away from demanding ownership towards renting. It sucks for me because I want to pay once, but I'm the minority I guess. Companies deliver what people are willing to pay for and the renters are absolutely demolishing the buyers. On iOS when you get a subscription for 1 month you can immediately cancel it right after buying and keep the service for 1 month, so then at least you can't forget to cancel. Kind of absurd that this is what I find myself doing.
The nice thing about the subscription model is that it gives companies an incentive to keep serving you after you paid I guess... -
Many people are even afraid to look like they put any effort in
-
I've read legends of a sage who would dictate his assembly language code to his secretary
-
It sounds like you're in the extreme wild west doing whatever you want and learning money skills in the process. This is an ideal setup for a self learner like you I think - if you were in a company with experienced engineers they wouldn't let you experiment like that and you might end up learning much less quickly. Definitely stick around there for a while and learn as much as possible
That said you can't stay in a place like this too long man. You are still at a fraction of your potential and somehow the most knowledgeable person there that's crazy -
good luck!
-
@true-dev001 listen I'm not an expert but I think you should forget about the design draft! You are definitely not running at anything close to full functionality
Just tell your boss honestly what's going on and they should be able to figure out that you need a real break where you're not thinking about work at all. It'll pay off for them as well because you'll come back 10x more productive
use the break to exercise, go for walks, be outside, never look at a phone or computer screen. Go to a zoo or a park or something so your brain can reset -
@true-dev001 what about other stuff in your life? Is you having a bad time @ work affecting what you eat? Are you getting some exercise?
-
@true-dev001 I have no idea tbh. When's the last time you had a vacation?
-
@true-dev001 worth a shot! come on cheer up plzplzplz
-
The way I cope with this is to bitterly denounce every other engineer on the project (and every other piece of software it's on top of) and how everything they wrote sucks because it's not exactly what i would have done
I keep repeating this to myself until it feels true to build up a strong reserve of sheer spite. Then I fan the flames of hatred by drinking 10 cups of coffee & listening to metal to boost my adrenaline. You can further adjust your mindset by avoiding social contact & judiciously dropping loud F-bombs. Now leverage that hate by redirecting it into productive energy! -
@Root LOL you? I would have bet against that
-
Remember those kids in school who used 5 different colored markers and had the most beautiful notes? They didn't become programmers :)
-
Yeah I used it to make some apps and it was nice in some ways but whenever apple changed something microsoft engineers have to scramble to make some buggy emergency patch and then you autodownload and get fucked
I eventually got more productive by blocking all autoupdates and making sure to do it only before deploying in 1 big orgy of pain & suffering . You can even move outside of visual studio if the app is robust enough and you're working on some logic piece that doesn't need a UI -
Your company uses xamarin for their app? First time I've heard this
-
That's so interesting. As an employee do you feel your job is so amazing that it justifies all of the effort people put into getting hired there?
Benefits lol. I think people just want the social status of working there. -
6v
-
i use vim in a console because i like the nostalgic feel of it, I don't actually think it helps me
sometimes I unpower my mouse and internet and force myself to use my phone when I'm stuck
to open a file i just type :edit myfile.txt
if i don't know the file name i use the terminal command ls to list files. In vim, type:
:terminal
ls
or if you want a 1-time terminal command type :!ls -
SEGMENTATION VIOLATION
-
You absolutely have to get over your shyness - asking for a raise is very important. There is also nothing embarrassing or wrong about it. If they do give you a raise it will help you a lot because your next employer will want to top it, so make sure to stay until you've received a full year of the new pay. If they decide not to give you a raise, leave the company for something else.
-
I think the ideal team size in tech is like 5 people
-
I'll try to answer seriously! Google engineers definitely are not dumb, but when giant swathes of humans form groups very strange things can and will happen. Smart people are actually even more susceptible to this
When you form a team of more than ~100 people, irrational stories are necessary for them to work together. Religions, politics, bitcoins, fashion, celebrities, money, justice, spaces vs tabs, human mass delusions are the norm, not the exception.
Programmers and managers are people too, and it's all but guaranteed that google has developed a unique arsenal of crippling delusions that keep their productivity in check. The amazing thing is that they sometimes manage to produce stuff -
@blindXfish I'm totally clueless about design patterns ^^ every time I've looked at it it deemed quite fishy to me
-
Hahaha classic. The person who rejected your way before probably sincerely believes it was their idea and they're helping you fix your errors.
Pro tip: try sarcastically apologizing / thanking them for fixing your error (without giving a hint with your voice, say it naturally) and see how quickly and naturally they accept and say 'dont worry about it' or something like that. You'll be amazed.