|
Progressive JPEG posted:Meanwhile, stuff like Android and open source projects just use plain git. AOSP uses `repo` which I think was a wrapper around Git written by an intern designed to manage multiple Git repositories, but under that it's plain Git. As far as I know they're still using it anyway, it's been a long time since I've messed with Android myself.
|
#
?
Jan 4, 2020 03:26
|
|
|
|
| # ? May 12, 2024 14:26 |
|
|
Plorkyeran posted:"This person works for company X therefore they are automatically masters of every single technology that has ever existed" is dumb even when it's not a company that has 100k employees. You can follow the twitter OP's profile to their github page where they have a bunch of non-trivial projects released. So at this point you're just running to the defense of a bunch of twitter users that likely saw she was a woman, then smugly posted ~~have you heard about git rebase~~.
|
|
#
?
Jan 4, 2020 04:15
|
|
|
git rebase is cool, Twitter reply guys aren’t.
|
|
#
?
Jan 4, 2020 04:56
|
|
|
Jose Valasquez posted:The git wrapper has been deprecated in favor of a mercurial wrapper instead. Both are too hard for me to understand so I just use regular Piper Look at this nerd who doesn't want to change multiple things in the same file in different changes.
|
|
#
?
Jan 4, 2020 04:58
|
|
|
Oh god, are we still complaining because we feel insecure around engineers that have been hired at google and are insecure about that insecurity?
|
|
#
?
Jan 4, 2020 05:19
|
|
|
Jose Valasquez posted:The git wrapper has been deprecated in favor of a mercurial wrapper instead. Both are too hard for me to understand so I just use regular Piper Why hg over git?
|
|
#
?
Jan 4, 2020 05:41
|
|
|
Xik posted:You can follow the twitter OP's profile to their github page where they have a bunch of non-trivial projects released. I'm not sure what's unclear. I complained about the claim that working at google means that she must know how to use git because that's a dumb statement. It's safe to assume that 98% of the responses she got on twitter were even dumber than that statement because people can never pass up an opportunity to "correct" obvious jokes, and there's plenty of reasons that aren't dumb to assume that she knows how to use git. Neither of those things are related.
|
|
#
?
Jan 4, 2020 06:36
|
|
|
captkirk posted:Oh god, are we still complaining because we feel insecure around engineers that have been hired at google and are insecure about that insecurity? I wasn't complaining but you scare me with your accuracy about my insecurities that I was unaware of myself.
|
|
#
?
Jan 4, 2020 10:19
|
|
|
The point is that she is a woman so a good 85% of people in tech* immediately assume she must be stupid because she is a woman. Additionally, this woman also works at Google, and about 90% of people in tech** do not work for Google, so obviously people who work for Google are stupid because they don't even understand a basic thing that they themselves sucessfully googled (heh) once. That means 175% of people in tech*** replied to the tweet and let her know that she is obviously stupid^2. We'll meet back here for another round of "endemic or epidemic, you decide!" next week, subscribe and like. *: I made up this number. **: I made up this number as well, though I believe very much it is absolutely correct ***: I excel at maths for engineers
|
|
#
?
Jan 4, 2020 14:05
|
|
|
lifg posted:Why hg over git? Because the people who wrote the git wrapper already got their promotions, improving it from there won't get you any more promotions but building an hg wrapper instead might  I don't know the actual official reasons but promo probably played into it.
|
|
#
?
Jan 4, 2020 15:40
|
|
|
Jose Valasquez posted:Because the people who wrote the git wrapper already got their promotions, improving it from there won't get you any more promotions but building an hg wrapper instead might There are actual, sensible reasons, though I'm not sure if anyone is allowed to look at them now since they might be ~~NeEd To KnOw~~.
|
|
#
?
Jan 4, 2020 15:46
|
|
|
Plorkyeran posted:I'm not sure what's unclear. I complained about the claim that working at google means that she must know how to use git because that's a dumb statement. It's safe to assume that 98% of the responses she got on twitter were even dumber than that statement because people can never pass up an opportunity to "correct" obvious jokes, and there's plenty of reasons that aren't dumb to assume that she knows how to use git. Neither of those things are related. I get it, you’re one of those nit picky pedantic engineers. So which one of the twitter replies smugly telling her how to use git did you make?
|
|
#
?
Jan 4, 2020 15:47
|
|
|
Jose Valasquez posted:Because the people who wrote the git wrapper already got their promotions, improving it from there won't get you any more promotions but building an hg wrapper instead might You'd think with all the smart people working there that someone would have a clue about designing incentive schemes to promote behavior that's good for the company.
|
|
#
?
Jan 4, 2020 16:23
|
|
|
ultrafilter posted:You'd think with all the smart people working there that someone would have a clue about designing incentive schemes to promote behavior that's good for the company. Sounds like something that won't get you promoted
|
|
#
?
Jan 4, 2020 16:36
|
|
|
ultrafilter posted:You'd think with all the smart people working there that someone would have a clue about designing incentive schemes to promote behavior that's good for the company. Instead they designed incentive schemes to promote doing things smart people like doing.
|
|
#
?
Jan 4, 2020 16:46
|
|
|
Cross posting this from the interviewing is terrible thread:refleks posted:When im working hard touching computers i often end up on SO as everyone else. The IDE the developer wanted was Jetbrains and the free IDE was Netbeans LOL
|
|
#
?
Jan 5, 2020 18:36
|
|
|
ratbert90 posted:Cross posting this from the interviewing is terrible thread: I can only assume that this was a troll posting.
|
|
#
?
Jan 5, 2020 19:10
|
|
|
There's a fine line between recruiters and trolls.
|
|
#
?
Jan 5, 2020 19:10
|
|
|
https://twitter.com/ryxcommar/status/1217871161712893953
|
|
#
?
Jan 17, 2020 01:24
|
|
|
joke's on that dude, he can only afford to rent a single room at that salary
|
|
#
?
Jan 17, 2020 05:35
|
|
|
I put my hourly rate at 69 for a while for more or less the same reason.
|
|
#
?
Jan 17, 2020 07:00
|
|
|
http://svn.cacert.org/CAcert/CAcert_Inc/Board/oss/oss_sabotage.html I just learned about this old OSS manual on how to subtly sabotage enemy organizations, and apparently a lot of managers are secretly CIA saboteurs. General Interference with Organizations and Production posted:(a) Organizations and Conferences General Interference with Organizations and Production posted:(b) Managers and Supervisors also General Interference with Organizations and Production posted:(12) General Devices for Lowering Morale and Creating Confusion Why is the CIA spying on me?!?!?!
|
|
|
#
?
Jan 17, 2020 14:04
|
|
|
Keetron posted:I put my hourly rate at 69 for a while for more or less the same reason. god i wish i made 69 an hour
|
|
#
?
Jan 17, 2020 14:23
|
|
|
SimonChris posted:http://svn.cacert.org/CAcert/CAcert_Inc/Board/oss/oss_sabotage.html I feel like I'm in on the ground floor of a 100 LinkedIn posts and eventual Ted talks
|
|
#
?
Jan 17, 2020 14:45
|
|
|
SimonChris posted:http://svn.cacert.org/CAcert/CAcert_Inc/Board/oss/oss_sabotage.html What’s that phrase? Never attribute to malice what can be attributed to stupidity?
|
|
#
?
Jan 17, 2020 15:26
|
|
|
SimonChris posted:http://svn.cacert.org/CAcert/CAcert_Inc/Board/oss/oss_sabotage.html Protocol7 posted:What’s that phrase? Never attribute to malice what can be attributed to stupidity? Well, CIA had to learn it from somewhere
|
|
#
?
Jan 17, 2020 16:22
|
|
|
quote:(e) Act stupid. I just want to call out that I appreciate this being mislabeled as e instead of c, whether or not it was intentional.
|
|
#
?
Jan 17, 2020 16:51
|
|
|
Inacio posted:god i wish i made 69 an hour A lawyer makes about twice this.
|
|
#
?
Jan 17, 2020 18:05
|
|
|
I feel like you buried the lede, which is that dude's glorious Twitter banner 
|
|
#
?
Jan 17, 2020 18:15
|
|
|
Keetron posted:A lawyer makes about twice this. 
|
|
#
?
Jan 17, 2020 18:24
|
|
|
That chapter of the Simple Sabotage Field Manual is legitimately one of the most practical management books ever written.
|
|
#
?
Jan 17, 2020 18:55
|
|
|
 The highest tier tax rate over here is 51% and it starts at 68K, before that it is 38% But please, lets go back to coding horror stories. Right now I am refactoring some code from a prima donna dev that recently left which is the only reason I am allowed to touch it at all. - Makes an interface for every class so that he can use the interface for stubbing. Sounds sensible, if there was no such thing as Mockito. But "no you cannot use mockito as you cannot trust a framework!" as the only and only argument was a bit weird. - REST standards are for dummies, you should put all your query parameters as path parameters. No, I will not document what path is what parameter, you can see that in the code, can you not, you dummy?! - Depending on the response from the repository, I will have the controller return an error. NO! Not throw an exception, you need to construct your response in the controller. You cannot trust error handling in Spring! Did you not know that, you dummy! - You know what, I will make a Kotlin `open class` that can wrap around two very different objects, one if the response is OK, the other if something is wrong and return those to the controller. The controller can then build the error message from scratch depending on the type of object that is returned. Aint I smart? Interfaces and wrappers are awesome! - You need to start up the service using `SpringRunner::class` when unit testing, else you never know how something will behave when it is in the actual application. Now I am slowly moving all logic to the service layer, all controlling to the controller and have the service layer throw proper exceptions and let Spring Boot take care of the rest. Also ripping out all the useless integration testing that are unit tests in disguise. edit: the actual worst part is that he was a senior in the team and he was mentoring two juniors that now say "if you explain it like that, it did sound weird but he got so upset if you questioned his ways."
|
|
#
?
Jan 17, 2020 19:06
|
|
|
This is the Twitter banner of someone with an employee being paid $69,420. I'm ok with this as well.
|
|
#
?
Jan 17, 2020 19:11
|
|
|
Keetron posted:- REST standards are for dummies, you should put all your query parameters as path parameters. No, I will not document what path is what parameter, you can see that in the code, can you not, you dummy?! I had to deal with consuming stuff like that a few times for customers. It's usually some lovely marketing company that totes has an API!! My favourite was the one that had parameters in the path, but they weren't named. Some of them were optional. How do you tell the API that number belongs to that optional argument? Well, apparently you can't. 
|
|
#
?
Jan 18, 2020 10:51
|
|
|
I worked on an integration with a client that was, holy poo poo, a total shitshow. Their documentation was basically nonexistent (they had a JSON schema documented in a loving Excel document and some Word documents floating around that nobody could manage to keep up to date, apparently), inconsistent, ambiguous, and incorrect (why is this field optional? it's not! But it won't return an error!). The API was a garbage fire that returned meaningless error messages when it did return error messages (with status code 200, of course), and they were unresponsive and outright hostile when we asked them questions. Their logs were useless and they clearly didn't know how to parse them, so they had to have us send us what a successful request looked like so they could tell us why later requests after we made a change were failing (they were wrong, their suggestion was incorrect, so rather than fight them we just rolled it back). This is a multi-billion dollar company that I'm sure a lot of people in this thread actually deal with and I'm so, so, so loving sorry.
|
|
#
?
Jan 18, 2020 16:12
|
|
|
A third party cloud server provider gave us explicit instructions to "make API call A first, then wait at least 5 seconds, and make API call B next." API call A is designed to ping an IoT device simply to wake it up such that it can receive further commands. It doesn't take 5 seconds to wake the device - it takes 5 seconds for their cloud to do whatever the gently caress and then call the device. That was at the start of the project and as I'm sure you can imagine the performance of the cloud API has only gotten worse. This project also includes Alexa/Google Home automation. If you've ever developed an Alexa skill, you'll know the window for device descovery is like, 8 seconds max? So having to wait 5 seconds gives you next to no wiggle room. We came onto this project halfway after the original client had already cut every possible corner so it's, uh, been an experience. Did I also mention that sometimes you have to make API call B twice because the API will sometimes send different results or return nothing at all? Jesus Christ, I could go on and on about this project. Macichne Leainig fucked around with this message at 16:23 on Jan 18, 2020 |
|
#
?
Jan 18, 2020 16:19
|
|
|
My favorite vendor API thing was with a vendor that kept pointing to the docs when I had questions so when I found a difference in behavior between the API and the specs and pointed that out, they said nothing but without warning changed the API a week or three later. gently caress everyone who integrated with the actual instead of the documented use, I guess?
|
|
#
?
Jan 18, 2020 16:47
|
|
|
Keetron posted:My favorite vendor API thing was with a vendor that kept pointing to the docs when I had questions so when I found a difference in behavior between the API and the specs and pointed that out, they said nothing but without warning changed the API a week or three later. gently caress everyone who integrated with the actual instead of the documented use, I guess? We're supposed to be goddamn mind readers apparently. I spent two days trying to debug this because I didn't expect them to change the status codes. Ghost of Reagan Past fucked around with this message at 16:58 on Jan 18, 2020 |
|
#
?
Jan 18, 2020 16:51
|
|
|
I enjoyed using a library from a DRM vendor and then writing their test suites for them to explain why certain API calls weren't working when they didn't understand or refused to understand. Their site to submit issues also required MSIE 7 (years ago but it was still out of date) but spoofing the browser agent worked fine. They were still the best choice by virtue of having a demo code sample that actually compiled instead of pointing to their developers' computer's file systems absolute paths, or just mysteriously missing parts.
|
|
#
?
Jan 18, 2020 16:54
|
|
|
|
| # ? May 12, 2024 14:26 |
|
|
Ghost of Reagan Past posted:I spent two days trying to debug this because I didn't expect them to change the status codes.
|
|
#
?
Jan 18, 2020 17:23
|
|