515 karma · joined March 21, 2020
The only advice from the article I liked was:
> Even if it's just "hey, can I come sit in on that meeting?" Take notes for yourself of anything you're unfamiliar with and ask about those things later.
I love sitting in on meetings just to take notes. Recently some Sr Developers and our DBA set up a weekly meeting to discuss overhauling our database schema and I asked to sit in. Even though most of what I heard aligned with what I already knew I still got a lot of value in just listening to other people's opinions. The DBA was a fountain of knowledge when it came to the nuances of using SQL Server.
I am really grateful that I was in a position where I was able to go to college to learn. My parents allowed me to live at home rent free for 3 1/2 years while I worked a full time job on 3rd shift. I took 2 classes a semester and I didn't go into any of the schools degree programs. I paid mostly out of pocket and took whatever classes I thought would be useful. I took almost every CS class, a UX class, a few graphic design classes, some business law, project management, and an accounting class. My advisor was always seemed really concerned I wasn't working towards any particular degree. I never looked at my grades and never stressed about passing any exams because they didn't matter to me. All I wanted was to pull as much knowledge as I could out of a class.
If I need to insert myself into a discussion I play dumb by asking a lot of questions even if I have knowledge/experience with the subject. To present alternative ideas I'll ask things like "Why wouldn't X work here?" or "What are the benefits of doing {current thing} instead of {what I want}?". Since I'll already have knowledge of the subject I can mostly tell when their responses don't make sense and I'll continue asking to follow-up questions trying to get them to see things from my perspective. I've done this a lot and it seems like it's a 50/50 shot that they'll be open to trying your ideas.
I've had to create and consume these type of APIs. Demoralized and unproductive has always be the result I've gotten.
I work on a small team (2 backend devs, 2 frontend). The we are always arguing about the API. The frontend devs want the data for their components pre-formatted in 1 API call. The backend team wants to run a SQL query and return the entire record as JSON.
I've been using Midjourney to create logos for my FOSS projects. In the past I'd never spend money on something I'm making for free but now I just generate a few variations of a prompt like "create a minimal flat vector logo for a software product called X" and I pick the best one. I don't need a logo for a FOSS project but the barrier to entry is so low there isn't really a reason not to do it. I still pay humans to design logos for products I want to market because AFAIK there isn't really a great way to do minor revisions with Midjourney.
I find the idea of being an expert in a language acceptable if it's been used for long enough. Almost all of my coworkers only know .NET and there are enough jobs needing people for new projects and legacy projects that they most likely won't have to learn anything else.
> or tool y
This is where the absurdity begins for me. I have a coworker who is 5 years into his career with the title of "senior react engineer". He started as a "junior react engineer" and at this point only knows how to solve problems with React. He has limited knowledge of the underlying language or general CS concepts. Every problem he encounters can and will be solved by installing NPM packages.
These are the things I struggle with when designing generic corporate marking websites. I'm not a designer but I've worn the designer hat many times. I always warn my employer/client that I'm more of a technical designer than a creative one. Nowadays I just stick to application design since it's 100% technical.
Example: as someone who's more technical than creative I could have come up with the overall layout of the Excalidraw+[0] website but I don't think I would have thought about adding circles around keywords or the dashed line that leads users down the page.
Depends on the rendering engine. With Blink opacity, filter, and transform will skip past layout and paint after the first render.
Chrome Dev Summit 2018: https://youtu.be/AB9qSUhlxh8?t=754
I'm typically the type of person who keeps my opinions to myself unless asked and when I disagree with someone about how to do/build something I'll do it myself on my own time. Sometimes I'm right and sometimes I'm wrong. As much as it sucks to realize I'm wrong I do appreciate it because it means I learned something and my opinion has improved.
This has been my experience. I've attempted to use ChatGPC 4 times to generate a functions or classes with various levels of complexity and every time it has produced incorrect code. It often fabricates functions, classes, or entire libraries and the few times it produced regular expression the regexp didn't actually do what ChatGPT thinks it will do.
I've yet to get any traction on any of my open-source projects outside of myself, some old coworkers, and a few dozen random people. This morning while looking at someone else's semi-abandoned project I noticed there were 600 unaddressed open issues so I figured I would jump in and try to help some people. After answering the same question for the 4th time (linking them to the official documentation) I started to feel truly grateful that nothing I've released has become popular.
The icing on the cake is when I need to SSH into a server to debug some PHP or JS on a testing server. I know I can always open Vim for a slightly degraded (compared to my Neovim setup) but overall solid editor at any time.
I've changed jobs 3 times in about ~10 years and this has happened to me both times. I want to leave my current position but the anxiety of dealing with this again is one of the primary reasons why I haven't started looking yet.
What I think is worse is even when they have a formal background in UX the company never wants to utilize it. Every time it's the same junk process. Instead of deriving features from user journeys, empathy maps, and personas the company has the "UX" person generate documents that validate the feature list the customer already wanted, users be dammed. You can also forget about A/B testing or in-person testing the person at the top with a C in their title knows what their users "need" so there is no need to pay for testing.
import type X from "package"
So assuming you are pulling in PixiJS with a <script> tag you could npm install the PixiJS package just for the types. It could look like this:
import type * as IPixi from "pixi.js"
declare const PIXI: IPixi
Then when you compile all the "import type" statements will be removed.
I'd think that would be a pretty big sign that React might not be the right tool for the job. I'm all for building custom hammers but sometimes it might just be better to just grab a screwdriver.