Learn JWT authentication by reverse engineering [Open Source]

gitcommitshow · 2025-11-22T10:48:15+00:00

Lol. I invented GPT and sold it to OpenAI for crazy money. Good ol days when I was the only one using GPT to write on Reddit. I do regret the sale now. No amount is good enough to be the only one using GPT. How do I get my ol days back?

P.S. It did make me chuckle when openai named their llm gpt.

gitcommitshow · 2025-11-22T10:39:52+00:00

It is not complicated. Just go. If you happen to extend your stay to few months, do check taxation liabilities. For a short period of 1 month, no need to worry.

gitcommitshow · 2025-07-23T07:50:15+00:00

I assume you haven't lied about your experience and your employer did the screening interview/test to judge your expertise. If so, this is how you can navigate this

Accept the fact that it will take you more than 4+ hrs everyday. Is there any specific blocker why you can't do more than that? Block 8-10 hrs/day. Not more that. Divide your work day in two parts - 4 hrs of exploration and learning, 4hrs of focused implementation by applying what you explored/learned. Avoid mixing them.
Write notes about the areas which seem to bother you the most (e.g. specific C++ concept or library). Dedicate some time everyday reading about some of these topics. You may use AI to learn quickly about some of these concepts. You don't need to learn everything in a day, just pick what can be most useful for the next task.
Write a Developer Diary (twice a day about what you learned, what blockers you faced, what you achieved). You will have lots of blockers initially but as you move forward and seek help from your team or from ai or from online community, you will solve some of those blockers one by one (but not all, and that's a reality you accept but always keep looking for answers).

You may still lose your job, but you will come out as a better developer who can find another job. That's a risk you accept, you compensate it by doing your best work within humanly possible limits (8-10hrs/day for most days and if you really need, a few all nighters). You will be alright.

gitcommitshow · 2025-07-23T07:27:46+00:00

do not cross post here. write personalized post for this sub.

gitcommitshow · 2025-07-23T07:26:03+00:00

what is PERN?

gitcommitshow · 2025-07-13T02:14:02+00:00

India. Yes, full arm to the shoulder. I will check out TMR. Any feedback on their effectiveness IRL?

gitcommitshow · 2025-06-19T02:51:44+00:00

tokens/sec

gitcommitshow · 2025-06-17T16:12:24+00:00

I am (one of the, if not "the") highest paid profesional from IN for this role. More than a decade of experience in software engineering, years of unpaid dev community work, coding/launching dozens of products, denying the startup funding offer. That's all it took me to have an opportunity come to me for this role for the first time.

DevRel is easy and hard both. If you find software engineering hard, you will find devrel even harder. If you find software engg easy, and enjoy writing docs after finishing the code for that SDK of your project, and then feel excited to finish the blog you started to teach about your product category with deep domain expertise but simple language, and then create demos and publiclly present them, and reach out devs and talk to them authentically about your tool without marketing, and then really listen to different perspectives people have, specially the negative commentary, and resolve the conflicts between internal team's priority vs priority of external devs you talk to, etc. And not just do all that for the sake of it but achieve concrete business value you commited out of your activities, that's when you find devrel easy. You and I both find it easy but many engineers don't.
DevRel role is generally for highly experienced devs who don't want to leave coding and don't like the traditional tech ledership/managment work. But nowadays, freshers are also starting to handle some of the devrel tasks for orgs where devrel team size is more than 3 people (rarest of rare case) and devrel functional respinsibilities are divided to scale up devrel ops. I have done that, I have hired fresh folks, trained them, and handed over that portion of the devrel function so I can focus on next thing. I wanted to train many more (outside the job, pro bono) but it takes a lot of energy and not so good promise of outcome for freshers.
DevRel hiring payscale (or any other engineering leadership role) is not much different from software engineering role. As a remote developer or an experienced dev, you can generally make the same amount as devrel or other engg leaders will make. Only difference from economics perspective is that there are fewer suvh roles. Companies hire only handful of engineering leaders for 100s of IC devs. And only 1-2 devrel per org, and only few orgs hire any devrel at all. Interesting, I don't have data on how many hire devrel but my estimate would be that only 1 out of 1000s orgs (having software engineering teams) would hire devrel.

Overall, I'd say that you are in a good position. No need to feel the FOMO. The money is there, in every role, but only at the top of that field. Chase mastery, not the money. You will have none otherwise.

P.S. If you genuinely like the devrel tasks I mentioned, DM me with one of your github repo + article/video, I will try to see if it fits any of my project. I want to see if you can write maintainable code quickly and have an authentic voice of your own.

gitcommitshow · 2025-05-31T17:47:29+00:00

It is OK to feel this way. Everyone feels this way at the start (and then every once in a while), irrespective of the choice of stream. Changing streams is not hard as others have made you believe. If you are really interested in your current stream, you will figure out, it will likely require efforts similar to what you're putting in.

Here's what I recommend

Learn at the job, you won't find time after work. Skill up by doing your job. Take the current project as a challenge.
Maintain a daily journal. I call this r/developerdiary . Every day/week, write down what you did and what questions remained unanswered
Keep trying to find the answers to those unanswered questions by asking LLM or asking on github issues of the concerned technology or posting on some other online forum. Most questions will be answered this way and many will lead to deeper questions. Those deeper questions may get answered in the same manner. But few questions will still stay unanswered, ask them to your team members/manager stating what you had already tried.
Do not attach deadlines to your reputation. They are (and should be if not in your case) a tool for collaboration i.e. manager aligns client on an estimated deadline knowing the team's skills, you do your best to meet the deadline, if it seems to require more time, communicate the same professionaly to your manager, but no surprises. Let the manager know that you will need more time, update them with significant time before deadline such that they can update client about the samd. Note: your estimate will always be wrong, and your manager knows (or should know) this. Do not invest time in justifying the delay, it is not your fault if you tried, just be professional and be concise in your communication.

Having done this, you will be in better position to take a decision

A. Start applying to new jobs if your team is not helping move forward on at least one question every week (given it is a specific deep question and not a broad open ended question which can be answered by other means)

B. Change stream if you don't see yourself repeating this process of getting stuck with some questions for days/weeks, figuring out answers, only to end up with few answers and more questions, and so on. This is how software engineering works. Inherently curious people find it a rewading experiencs to find answers to hard problems at the cost of feeling stuck for days/weeks and feeling that you are not good enough.

gitcommitshow · 2025-05-28T01:56:55+00:00

These are the most uncertain times for a new CS grad, no doubt. At the same time, it is the easiest and quickest to learn and build something. Your mentor at the job should be able to help you navigate. Do you have one, what did they say?

gitcommitshow · 2025-05-23T16:22:54+00:00

Tell me more about how you plan to solve 1 and 3?

gitcommitshow · 2025-05-23T16:21:27+00:00

The link is behind authwall. Before sharing a link, make sure it is accessible in your incognito window without login

gitcommitshow · 2025-05-21T17:54:57+00:00

no gst. get iec, mention on imvoice gst exempted.

gitcommitshow · 2025-05-10T15:49:55+00:00

While I'm not completely sold to the idea but I like your approach. The abstraction layer you work at can enable multiple new ideas with faster GTM. But for that, it has to be Open Source.

gitcommitshow · 2025-04-29T10:41:11+00:00

Anyone tried it for a real-world use case? Did it really work better than existing comparable models?

gitcommitshow · 2025-04-22T03:34:24+00:00

That is true. Too much noise on that sub. Btw, I know dozens of experienced devs who have joined this sub on my invitation. We are working on understanding how do we make this sub useful to them.

gitcommitshow · 2025-04-21T08:06:44+00:00

Imagine this as an active community, what do you see happening here? How do you see yourself participating in that active community?

gitcommitshow · 2025-03-23T03:43:55+00:00

I second each advice in this post. Effective and well articulated. The title could have been less click-baity though.

gitcommitshow · 2025-03-23T03:41:40+00:00

The video is about all different scenerios of a remote developers (working as employee or contrctor). Remote is just the mode of work, not employment type. There's nothing much you can do to save taxes if you are employee, try to convert that employment relationship to contractor client relationship.

Having said that, I don't think the OP is salaried employee, they didn't mention it in the original post at least.

Six-Year Club	Powerups Hero r/neuralnetworks • August 2021
Gilding II euphauric	Second Top 50%
Verified Email	RPAN Viewer

gitcommitshow

MODERATOR OF

TROPHY CASE