muhanga

joined 1 year ago
[–] [email protected] 2 points 8 months ago

Tldr; take offer, don't quit engineering yet, you are fine

Don't quit engineering if you enjoy it. If you have better offer and the current ship is leaky as fuck => jump the ship. Saving the leaky ships should be very profitable if it is not => you are being heavily exploited.

I jumped the ship thrice. And one time accepted a lower payed position, just because I was quite burnout.

On the topic not using the progress and not understanding the Intenals. Understanding internal will not make you senior. Understanding what you can apply that you already know can make you senior. I remember being in a situation like yours. I thought I didn't know Jack, but then on a newplace I seen people who were running around like a headless chickens on crack. This has given me a good understanding about what knowledge is and that applicable knowledge is the key.

[–] [email protected] 3 points 8 months ago

Coding interviews are a decent way to screen out the false positives. Watching someone solve coding challenges gives you some assurance that they can, well, code.

Hahahahaha. If only. There is very big distinction between ability to priduce code that solves the problem and solving the problem. My personal experiense showed me that passing the coding interview and being a good Software engineer is a two different skills.

[–] [email protected] 5 points 9 months ago

Is it possible to build XML parser in it?

If answer is yes then i will build XML parser in it.

Solving a problem you know how to solve and solved more than once is a my goto approach in learning languge or frameworks. Translation of already solved problem to the new operational model or semantic exposes a lot internal stuff and marketing double talk.

This is a lot of work and time so can not recommend it for all cases and situations.

[–] [email protected] 2 points 9 months ago (1 children)

in many cases for text docs I'd rather write them using markdown and maybe add some html styling then convert with pandoc

Yep. Exactly the case. Using the multiple instruments instead of one "specially created for this reason" programm become normal. And it become normal because the program become unpredictable in changes. All the functionality is click away, but you need to know what to click.

And as a chery on top Outlook by default uses ctrl+f to forward a message. Instead of starting search.

[–] [email protected] 9 points 9 months ago (3 children)

I wholeheartedly agree with that. Every version of Excel is massively worse than previous one. Same with the other Office products. Incremental fixes and impovements covered with unneded features and Ribbon design.

The Ribbon interface intoduction is the most obnoxious design decision that was pushed to the keyboard and mouse users. It only helps "touch" or "pen" users and only marginally.

Then OneDrive aka "we holding your data ransom" Drive. This is the only one Drive that is purelly sheit.

[–] [email protected] 8 points 9 months ago* (last edited 9 months ago)

Which OOP? Alan Kay meant this:

OOP to me means only messaging, local retention and protection and hiding of state-process, and extreme late-binding of all things. It can be done in Smalltalk and in LISP. There are possibly other systems in which this is possible, but I'm not aware of them.

But there is also various other OOP around. And those really about completly different things.

[–] [email protected] 1 points 9 months ago

This is a good example of what understanding your tools can give you. Answer is new or novel approaches to the old problems. Ability to create a patch from any diff is really really usefull. If you have wip changes, but don't want to commit it to, then creating a patch is a quite easy way to go.

[–] [email protected] -2 points 11 months ago

If you use a programming language which behaviour depends on the symbols that you hiding 90% of the time (I am talking about line ends and whitespace types) you will have a bad time. No amount of gitattributing or autocrlf magic will save you. You will suffer and you will get a phantom bugs if your editor and diff viewer will not show you "whitespace" changes.

And at the same time any programming language that will break due to whitespace should be chastised and laugh upon. Whitespace type should never be significant modifier for behaviour.

Also YAML can fuck off right into the sun.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

And sadly one more font I will never be able to use due to missing support of non-latin characters.

Sadly some features are nice.