Born a sconie right on Lake Michigan, lived in Iowa for a handleful of years for college, then moved to Sota where I live currently. Software Engineer for 20+ years, Ham Radio Operator, lover of retro graming, old time radio and the outdoors.

Mastodon: jecxjo@mastodon.sdf.org

  • 0 Posts
  • 43 Comments
Joined 2 years ago
cake
Cake day: September 9th, 2022

help-circle


  • I’ve always been amazed when i get a new “seasoned” project manager and they try to really work on making all the tracking as efficient as possible so they have tons of metrics.

    …and then nothing happens. We don’t look at projects and tasks and figure out which work would be best for which team members based on past experience. We don’t do any sort of optimization. We just track “velocity” and our estimates on release end up more dependent on how new the tech or the concept is (not knowing what we don’t know) than anything else.





  • I don’t think it matters what tools you use as long as it works.

    That would be true if other systems and services depend on them. Would have been nice to come out with a standard and designed systemd around that standard. Then you pick the tool you want that follows the standard rather than be tied into systemd.

    Worth noting is that a process not managed by pid 1 isn’t really a thing you want generally

    I would disagree. A compromised Docker doesn’t mean i have access to things managed by PID1. The entire control model is based around moving your publicly available services further away from something with the highest level of access. Be it users or processes.






  • You don’t have to actually do a real project. It’s more about doing a task that requires you to create outside the hand holding.

    After 15 years of OS and embedded systems development I learned web dev by creating a SaaS for my HOA’s property manager to communicate with tenants. Node, React, MongoDB, docker, iOS and Android apps. Did the project look good? Nope. Did I have to dig into manuals and debug for weeks, yep. But I easily stepped into a new role in an industry I had never worked in because I really learned the tech stack. Actually using the app wasn’t necessary, just that I actually had to create things requiring me to design around the technology I was learning.

    Pick a problem in your life and solve it. Doesn’t need to become something you sell or publish or even use after you’re done learning. But the point is to actually use your skills.


  • I’m saying that the work they would be doing in two days isn’t the same as solving an actual problem. The way to really learn a language/framework/library is to actually use it in a real project. You run into pitfalls, you get compile errors and have to figure out how to debug in said tech, you find out how extentions to the tech work so you can create your own. Making a Todo Front End isn’t going to cover the vast majority of the stuff I’d expect one to know or experience when you say you “know” a language/framework/library/etc.




  • jecxjo@midwest.socialtoProgrammer Humor@programming.dev“Hire me”
    link
    fedilink
    English
    arrow-up
    13
    arrow-down
    1
    ·
    1 year ago

    Because anyone worth their salt knows that the superficial hello world example covers the tip of the iceberg. So to say you learned it in two days means you either don’t get that you barely scratched the surface or you dont get what other developers really need when they hire someone with knowledge in a specific framework.


  • The problem was that my boss was a title hopper and needed to fill his old position and he did it with yes men who wouldn’t stand up for anything. Meant that these yes men were also not the greatest at doing the rest of the job either.

    They were expecting me to just do Hero Engineering by not objecting, put in more time and fill on the gap when theu couldn’t do their job. Was the first time in 20 years i ever was reprimanded, been praised at everything else I’ve done. So i knew at that point this was just a toxic place to work.


  • We aren’t talking about a bug, new feature stories. No screen shots, no identifieres to get me closer to a solution.

    For example one of my stories had the following as the total amount of text for the entire ticket: “Add parser for new message type.”

    Add the parser where? What is the new message type? Is this for a test tool or the project itself? Unit test framework? In a library or in the project code? We were working on two protocols and one protocol had a high level and low level message structure so i literally had 3 possibilities.

    And when i asked my boss what the ticket was about i was told that i should do some investigation and fill in the ticket myself. Wtf?!? When i then told my productivity was wanting i started looking for a new job.