I've been doing the "big ass text file" approach forever. This is a nice alternative that doesn't try to do too much. Enjoying it so far! Going to give this a real go to use it to plan out my next project.
This is great! Pretty similar to what I did in that you have actual links to the articles and even images. If you had a cron script that auto-generated new content every day, I think that would be the only thing that I'm doing that crackernews doesn't yet.
Another interesting choice is you are generating the article content itself. It is wild how you can get it to generate markup on the fly for different styles of posts.
For my project, I'm generating structured JSON with an [OpenAI Function](https://platform.openai.com/docs/api-reference/chat/create#c...) as I found even if you tell it the format you want in the prompt, it sometimes ignores it or doesn't match exactly. Then I'm uploading the JSON and images to S3.
I didn't realize you could get a DALLE image and drop it in your own directory with a oneliner like you have. Very nice!
I created this as a tool for playing around with different font and color combinations then generating a theme object that meets the System UI Theme Specification for creating interoperable UI components (see system-ui.com). The idea is that you can quickly experiment, and then if you come up with something you like, you can take those style properties and use them to make your component libraries or with popular projects like Theme UI, Rebass, Primer, Chakra UI, etc.
They did not actually buy the ad. They are simultaneously making fun of Super Bowl advertising and how easily people believe fake news (no fact checking that there was never a potato ad aired)
I am shocked by how few candidates have much of a Github profile at all. So the good news is that it is easy to stand out.
Have some projects that are finished. They don't need to be extravagant. Just show that you can ship code and know how to explain how/why to use it in the README or for extra points a nice gh-pages demo page. Once you have a few projects under your belt, you can create a nice home for them with your username by making a public repo with a project name of username.github.com - see https://pages.github.com
For front end, if you prefer codepen over Github as your online code portfolio of choice, that is fine too (at least in my opinion). Or both.
I removed the bit from the example where it mentions family. I think in some cases it is good to talk about the reasons why it is important to you to get a raise outside of just the money. It seemed to bother people and I think it is an optional thing anyway. Certainly not necessary in an email opener.
Everyone is different. I personally don't consider talking about why a raise is important to you, in a human way, is a bad thing. I wouldn't want to work for someone who thinks that what is most important to me in life is irrelevant at work.
I had that bit as optional because some people want to keep stuff like that out of it, which is fine.
The overall gist is that when making your case, if you truly like your company and want to stay, you do not want to come off as an arrogant, greedy asshole who is up for grabs to the highest bidder. You should come across as a loyal, enthusiastic, high performer who simply wants the salary (or possibly promotion) they deserve.
Sometimes getting you a raise will require your boss having to fight a battle for budget, and to do that, it helps if they actually like and respect you as a person as well as value you as an employee.
I have gotten many raises over my career, so this approach has worked for me. However, every situation and person is unique.
Maybe template is the wrong word. It is meant to be a loose outline of what you could say. A starting point with some advice. Every situation is unique.
Also, this email should function as the invitation to have a discussion. Finding the right time and way to ask for a raise can be difficult and stressful. Using an email to start things up can take the pressure off.
As stated in the intro, the email is meant to be the start of a conversation. Of course you can discuss it in person instead. For many people, it can be intimidating and stressful to ask for a raise. Sending an email allows you choose your words wisely and take some of the pressure off. Better to send an email than to keep waiting for what feels like the right time.
Some have suggested the tactic of threatening to leave as your negotiation tactic. I would recommend against that if you like working where you are, as it could backfire. You could even get that raise, but then later be let go. If you don't really like where you are working at all that much, then go for it (but maybe don't lead with that tactic as it can burn bridges).
For this little project, I just grabbed a template used by a very popular Github page. Looks like the font does not play well with Windows. I just switched it to good ol’ reliable Helvetica.
The social aspect is definitely important. Being someone who can work well with others is essential. Being able to communicate complex tech things to non-tech people is very valuable for career advancement. If this is a skill you lack, work on developing it.
If your manager thinks you suck, then yeah, you will not be getting a raise. In fact, they may be looking for a way to push you out. However, if they do think you are good, then understanding where you are pay-wise relative to the industry can be a good argument to make.
In my own experience, having popular open source projects, giving talks, and writing articles contributed to the overall picture of my value as an employee and helped me advance my salary. This obviously can vary depending on where you work.
Doing those things also were great learning experiences, and made me better at my job.
It certainly helped me feel confident that I was worth a raise, and comfortable in that if I did not get paid competitively, there would be other opportunities.
Also you mention bringing in more business. Depending on your company, doing those things can bring in more business.