> You absolutely need a space to talk candidly with your manager.
It's not so easy when you feel like you can't trust the people to whom you report. I'm in this situation after attempting to be candid about what I felt were missteps on the part of my manager and a director of engineering. After a scolding from one of them, and a veiled threat about my employment ending, I now feel like I just shouldn't rock the boat. I mostly dread my 1:1s with them, and I don't feel like those meetings are time well spent.
I could maybe understand if I had offered unsolicited feedback, but they asked for my opinion and I gave it honestly.
honestly.. if i were in your situation i would bet looking for another job..
Right now i have a really good relation with my manager to the point were i can him out to him if i need to and were i trust him to help me advance my career if he can and that he will not screw me over..
In the past i have being in a position were i was at odds with my manager and definitely could not trust him, as soon as i realized that i started looking for my way out.. The period between that manager being hired and i leaving that job was the most stressful period in my life.. never been so happy to be fired in my life..
Now, that was another life, i was young and single.. now i have a few mouths to feed so if i got in that same situation today i would not get myself fired like i did back then, but i for sure would look for another job..
Not at all. I feel exactly the same way. I'm also introverted, and to me "relationship building" in a corporate context often feels really contrived.
I want to bring as much value as possible to my employer, and I don't feel like I generate value by having 1:1s for the sake of having 1:1s. I jump through the hoop though, because I want a promotion and I'm concerned that I won't get one if I don't fit the norm.
1:1 should be the moment for you to discuss with your boss what you should be doing to maximize the value you bring to the company.. those things often are not as black and white as they seen..
it is also the moment you share your career goals with your manager and for you two to discuss the goals you should achieve to be eligible for a promotion..
unfortunately more often then not promotions are the carrot that companies dangle in front of us to make us work harder with no intention on ever giving us the reward at the end..
My plugin supports this, but only if I happen to know the shortcut. When I start typing...
border-radi
...for example, the plugin doesn't suggest...
rounded
...because I didn't type anything close to matching that.
It seems like the only way to benefit from Tailwind without having to switch between your file and the docs is to invest time memorizing the many, many, many shortcut classes that don't start with the same word or letters as the actual CSS property name you already know.
This is a good take here, even as someone who loves Tailwind, the intellisense should grep not just the class name but the contents. `leading` is an insane name for `line-height`
I hope what you describe will eventually be true for me, but so far the purported benefit of not jumping around isn't being realized. After 5 weeks of using Tailwind every day, I still have to switch between my file and the Tailwind docs fairly often to look up whatever shortcut classes I need.
So far I just miss CSS modules. Having my .tsx and .scss files both visible in split screen wasn't so bad.
You’ll start realizing the benefit more when you use it on multiple projects. Tailwind will be consistent across your projects where you can’t always say the same for custom CSS.
I've never contracted, but I'm in the exact same boat with regards to being someone else's full-time employee. Lately I've been struggling to stay even one year—I've been with 4 companies over the past 4 years! I'm a "flight risk". :)
And it's not that I don't want to work. I put 3-4 hours per weeknight into side projects, and another 8-12 hours on weekends. I have yet to make money on the side, but I keep hoping that something will succeed and I can run my own ship.
Perhaps you feel like you're chained in when you're working for an employer - I feel like it's a gilded cage. Yes, there's healthcare benefits, dental cover, bonus if I'm lucky, that kind of thing but at the end of the day I'm owned. My time is owned, my attention is owned and although I can pull the red cord and quit it's essentially bondage. Quitting becomes harder to do when you have a mortgage and kids, too. So you put up with it, and make yourself miserable, or put up with the misery.
But start working for yourself and all that goes away. You have CONTROL back - you dictate what you do, i.e. what you find interesting. Of course, the difficulty is making enough money to live, and finding that balance. I can't make money from side projects, I'm not that talented, but I can make money picking and choosing the projects that suit my interests and contracting is a happy medium.
I recently spent four weeks interviewing before landing a job, which is not an unusual amount of time compared to years prior (at least for me). The company I joined went from first interview to a good offer in two weeks—they were definitely eager. I put my application out approximately 50 times. Changing my LinkedIn status to "Open to work" helped.
The biggest difference this time around: Several companies invoked a hiring freeze while I was in the middle of their interview process. I've never had that happen before, so it felt like a storm brewing. Some were nice enough to tell me right away, while others went completely dark for weeks before getting back to me.
Good luck with the job search! I know it can be utterly miserable, but stay positive and keep those live-coding skills sharp as a razor.
I think we overlook wordiness too often! In fact, each "good" example in TFA can be shortened without losing context:
Good:
"I checked the foobar.py script and told Sarah that there was a bug related to updating the users table in SQL — the script does not seem to update the last name column."
Better:
"I found a bug in foobar.py and told Sarah it's not updating the last name column in the users table."
Good:
"Hi team, the email sending worker keeps crashing with the following exception. I've tried re-running, clearing the cache, re-installing dependencies. Can I get a hand?"
Better:
"The email sending worker keeps crashing with the exception below. I reran it, cleared the cache, and reinstalled dependencies. Can I get a hand?"
Good:
"The resource defines two routes, but the GET handler can only handle one of those — the one without any path params. I can technically make a request GET /api/foobar/123/456 and have the app crash with a 500 because there is a route but the handler doesn't take any params.
Roughly speaking, there are two "types" of resource endpoints — list and singular.
List type resource endpoints handle
- getting a list of resources: GET /things
- creating a new resource: POST /things
Singular type resource endpoints handle
- getting a single resource: GET /things/123
- updating a single resource: PATCH /things/123
- deleting a single resource: DELETE /things/123
To handle all cases properly, you need two resources:
...
"
Better:
"The resource defines two routes but the GET handler can't take path params, so a request to GET /api/foobar/123/456 crashes the app with a 500.
There are two "types" of resource endpoints:
List:
- get a list of resources: GET /things
- create a resource: POST /things
Singular:
- get one resource: GET /things/123
- update one resource: PATCH /things/123
- delete one resource: DELETE /things/123
You can have both of best worlds using BLUF: bottom line up front. I didn't read the code because it's too early to debug someone else's code, but here's an example:
These endpoints break REST conventions and will be harder to understand and maintain.
The convention is that GET /resources will list them, and POST /resources will create anew one. You can also use a path parameter to identify a resource you want to find with GET /resources/<id> or delete with DELETE /resources/<id>.
I find it useful for two reasons:
- maybe you parse the first paragraph and you have enough context to act, so you skip the second
- or you parse the first paragraph and form the big picture in your mind, and that will make it easier to dive into the details
reply