• 0 Posts
  • 297 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle
  • “Follow my path and you’ll be fine.”

    Later, at a Republic Tribunal:

    “… and obviously no sane pilot on a training mission would ever consider attempting to navigate those obstactles without weeks of study in advance. And so I exhort the jury not to consider leniency, but to find the defendant guilty of first degree premeditated murder of their wingman pilot in training. The prosecution rests this - quite frankly open-and-shut - case.”



  • Let your mentors know you’re looking for work, and how many hours you can work per week.

    New programmers provide negative value, so there’s not a lot of demand.

    I’m very good and studied hard, but my first couple of programming roles I got entirely because a mentor of mine recommended me to someone who took a chance on me.

    Also keep adding code to your public GitHub. Two of my top developers today I originally hired directly away from their retail roles. One had a ton of academic coding experience and had just not yet landed the right job. The other was just getting started, but posted a ton of low quality homework code to GitHub so I could read it and know who I was hiring.

    Edit: In contrast, one of my other top developers has one of the top CS degrees in the world. So that works too.

    And more than one of my top developers have IT help desk experience. I have had excellent luck when hiring folks with IT Help Desk experience.

    Edit 2: As someone else mentioned - your long term goal is to connect with an IT Recruiter that you trust, and work with them to get your resume, and GitHub, and/or binder full of code you wrote into shape. I’ve hired more than one candidate who admits the simply presented themselves exactly as their recruiter coached them to. And I’ve hired candidates I would have skipped, because their recruiter was someone I trust and they asked me to take a second look at a candidate who made a poor first impression.

    Edit 3: Since this is for newbies, some information about recruiters: we pay the recruiter in addition to what we pay you. The recruiter’s typical pay for a rookie hire is around $50,000.00, if you stay for a full year. Half up front, in case you don’t stay.

    A few things you should know about recruiters: they only need to make a few solid placements each year to earn a living. As a rookie, you’re the hardest to place, and the lowest layout when placed. But, programmers that are easy to place don’t move often, so recruiters may still have plenty of time for you.

    The recruiter is probably mainly placing you the first time in hopes that you come back later when you’re worth big money. The initial payent is nice, but the real payment will be if/when you have 5 years experience and still work exclusively with them.

    Hiring managers like me have recruiters we trust and reuse. If you can get recommended to a great recruiter, they will get you interviews at better places to work.

    In contrast, there’s lots of mediocre recruiters out there. Don’t be afraid to switch to a new recruiter, if you have the opportunity, and your current recruiter isn’t getting you interviews.



  • When something that big barely turns a profit, I immediately suspect Hollywood accounting.

    But if true, they made a game, covered their costs, left the company with an asset that can keep making sales, and probably developed their in-house talent and tooling along the way. That’s a lot of points in the “win” column.

    Wise leaders understand that, in business, victory means getting to try another project with the same team, next year. Failure means disolution of the business. Earn enough years and projects with the same team in a row, and maybe you take one of the big wins one of those years.


  • This is terrific. Thank you for starting this discussion.

    I don’t think we can or should wait for individual users to make these decisions. Server admins are the ones who understand the risks and so should make this call. Guidance for server admins based on past experience (cough XMPP!) should be quite welcome.

    I might refine the bit about altered API versions to really focus on the real problem: proprietary extensions. We probably want to leave the door open to try out additions to the spec that come with detailed RFCs.

    But we know from XMPP that proprietary extensions are a huge problem.







  • If you’re interested in that level of control, it’s time to look hard at GrapheneOS. “Internet” is a permission you can grant or deny for each app, under GrapheneOS.

    But I’m not aware of a way to selectively direct phone traffic through Proton VPN, at the phone. Even on GrapheneOS.

    Enough skill with an expensive router could do it, but only on your home network, or only while routing all of your phone traffic back to your home network via yet another VPN.

    Edit: TIL, Proton VPN supports split tunneling. Sweet! Look under Settings - Advanced - Split Tunneling - then pick your apps to include/exclude.

    Edit 2: TIL DivestOS also supports “Internet” as a per app Permission. Very cool.





  • I liked the big reveal, but I can see how it wouldn’t be everyone’s cup of tea.

    Partial Spoiler

    Normally when Trek is going to do a Trelane or Q story, it’s introduced early in the story. This was a weird left turn at the end, and leaves us wondering if any plotline later will also do so.

    I didn’t mind it in this season, because the season was so focused on about values and tradition, so I wasn’t expecting a hard scifi conclusion. Realizing they were ‘doing a Doctor Who’, wasn’t too shocking to me.

    But as much as I thought it fit here, it’s a weird way to resolve a Trek season, and I hope we don’t get that approach often.