|
Yeah I have periods of downtime at my current job and I just dig in and learn as much as I can about the tools/languages I work in or write stuff that will help me down the line. I've built a few components that ended up saving me (and some of coworkers) a lot of work on later projects. Also read the forums.
|
# ¿ Dec 11, 2015 16:13 |
|
|
# ¿ Apr 27, 2024 09:12 |
|
Is pair programming something people actually spend a majority of their working hours doing? Standing over a coworker's shoulder and going over something every once in a while is fine but doing it all the time sounds like the most miserable thing in the world.
|
# ¿ Apr 18, 2016 14:51 |
|
Does anyone's office not basically shut down the last week of December? All my jobs have allowed carryover and it's still always a ghost town between Christmas and New Years.
|
# ¿ Jan 28, 2017 00:03 |
|
Here's our PR process: 1. Break tests 2. Create PR without running tests locally 3. PR build fails 4. Reviewer merges without looking at code or failed build 5. Develop build fails 6. "Must be a problem with the frontend"
|
# ¿ May 8, 2017 15:38 |
|
Yeah if I had to work in an environment that used spaces I'd demand more money too
|
# ¿ Jun 16, 2017 20:15 |
|
Let me introduce you to Visual Studio Code my man
|
# ¿ Jun 20, 2017 16:41 |
|
Volmarias posted:The canonical rant is "PHP: A fractal of bad design". Jesus Christ it just keeps going
|
# ¿ Jun 29, 2017 03:43 |
|
We're using Elasticsearch as our sole datastore and then ended up setting everything up with basically no analyzers anyways because we never use text search and only do exact and wildcard queries
|
# ¿ Jun 30, 2017 18:44 |
|
Tbh your editor/gofmt/etc should just do all of this transparently. I had to double check because I wasn't entirely certain whether or not I had actually been using tabs for the past year
|
# ¿ Aug 22, 2017 20:32 |
|
Out of curiosity, what did your primary care physician say when you asked them how many hours they spend practicing medicine in their free time?
|
# ¿ Oct 20, 2017 23:19 |
|
It goes beyond passion for me. I will not apply to any job that doesn't have the phrase "rockstar" in the description
|
# ¿ Oct 21, 2017 01:09 |
|
This week when my family gets together to watch football, and my brother spends the entire game reading medical textbooks like he usually does, I'll give him a silent nod and he will know that I too read a blog post about a new Javascript framework outside of work hours
|
# ¿ Oct 21, 2017 01:18 |
|
There's a counter to the left of each line that tells you how long it should be. It makes all your code look like pizza slices
|
# ¿ Feb 5, 2018 15:45 |
|
Love that the nightmare union scenario is having a sysadmin reboot a server instead of a developer
|
# ¿ Feb 20, 2018 00:47 |
|
My last job doing internal web apps at a DOD organization our testing process was: 1. Send customer an email linking to our dev server 2. Customer never looks at it 3. Assume everything is fine 4. Fix issues on live production code
|
# ¿ Jun 7, 2018 14:44 |
|
Calling everything you don't like "lazy" is lazy!!
|
# ¿ Jun 18, 2018 17:56 |
|
I was really impressed by your background!
|
# ¿ Jul 14, 2018 14:53 |
|
You've been promoted. Roll d8 + CON for additional sprint points
|
# ¿ Jul 23, 2018 23:35 |
|
Technical Reverse Mortgage?
|
# ¿ Jul 25, 2018 00:40 |
|
Not true, sometimes things work great right away, and then suddenly stop working
|
# ¿ Aug 21, 2018 13:41 |
|
Yeah that's my favorite: "I'm not done yet but I'm gonna hit run anyways to see how it brea--wait why did that work something is very wrong"
|
# ¿ Aug 21, 2018 14:24 |
|
I always put incorrect expected values the first time I run tests just to make sure it can actually fail
|
# ¿ Aug 21, 2018 15:54 |
|
Volmarias posted:You should be adding tests for unhappy paths along with tests for your happy paths. I'm not talking about unhappy paths, I've seen incorrectly written tests passing when they shouldn't so now in my paranoia I force them to fail first and then fix it
|
# ¿ Aug 21, 2018 16:03 |
|
the only ethical consumption under capitalism is application/json
|
# ¿ Feb 7, 2019 15:10 |
|
I recently had to explain to a senior dev why he couldn't copy the -d '{json...}' argument from a curl command and stick it on the end of the URL string in a Javascript request
|
# ¿ Mar 11, 2019 23:53 |
|
for me it's called Week 2
|
# ¿ Mar 20, 2019 19:13 |
|
tbh I could not care less about True RESTful Standards or what HTTP methods you use or how you pass args as long as you provide some sort of OpenAPI/etc schema so I can generate a client
|
# ¿ Apr 5, 2019 17:47 |
|
was just in a 3 hour meeting discussing this exact problem
|
# ¿ Jun 12, 2019 14:17 |
|
just got to stage 3 I want to die
|
# ¿ Jul 16, 2019 19:33 |
|
One time on one of our internal apps for fun I made it so the user could customize their own color scheme It was basically Hot Dog Stands all around
|
# ¿ Jul 29, 2019 17:25 |
|
one weird trick to never have to give raises again
|
# ¿ Jul 31, 2019 17:25 |
|
TBH the answer is going to be highly dependent on the nature of the data and how it's being used. I wouldn't say that "I don't want to GET/POST the whole thing" is a very compelling reason by itself. Is there some reason why a complete GET/POST is expensive? Is latency a major concern? Are they doing bulk updates of single fields? Is the thing they really want to do something that would be better served by a new API (e.g.: update by query)? Does every other API already implement this as a standard? Regardless the question isn't "what is the best way to do this?" it's "is it worth spending the time to do this?" and it's not up to you to come up with that justification, and possibly not up to you to make that decision.
|
# ¿ Aug 21, 2019 23:07 |
|
I wouldn't do anything without some real metrics on how much these operations are actually bogging down your servers. He wants you to make a new API and then rewrite a bunch of client code to optimize a REST call that happens once every few minutes?
|
# ¿ Aug 21, 2019 23:28 |
|
If you do decide to help him the answer is probably not writing a generic JSON manipulation API but just giving him an Update Progress endpoint
|
# ¿ Aug 21, 2019 23:52 |
|
At my last place there was a guy who would come in before 5 (AM). Most everyone left between 2-3. I came in at like 10-1030 and had the office to myself for 3-4 hours every afternoon it was loving great.
|
# ¿ Sep 10, 2019 23:35 |
|
My current experience with Jira is improved by coming from a place with a nightmarish custom Remedy setup
|
# ¿ Oct 4, 2019 17:15 |
|
"Do you know why <thing> isn't working?" "What do you mean by not working?" "I'm trying to use it and it's giving me some error" "What are you trying to do?" "Well I'm trying to do <process> and it's giving me an error" "At what point are you getting an error?" "Doing <thing>" "Through the UI? From another service? cURL?" "cURL" "What's the error? "I'm not sure, some kind of access error or something" "What's the http code?" "I don't know, do you need that?" "Just send me the cURL command" ... "You put -X instead of -H for a header" every day with this poo poo
|
# ¿ Nov 20, 2019 17:10 |
|
Keetron posted:The above post but with: See also: The system is down
|
# ¿ Nov 20, 2019 19:51 |
|
"Hey has anyone told you yet that the system is down?" "What? Production?" "No, R&D" "It looks like everything is up and healthy" "I'm looking at the UI and there aren't any jobs running" "Are you trying to run something?" "No" "Is something supposed to be running?" "I don't know" "Are any of the data feeds turned on in R&D?" "I don't know" "If nobody is testing anything right now you're not going to see any jobs running in R&D"
|
# ¿ Nov 20, 2019 20:00 |
|
|
# ¿ Apr 27, 2024 09:12 |
|
Please no one fall for the "I can't right now but give me 6 months" line
|
# ¿ Dec 15, 2019 03:56 |