• 0 Posts
  • 106 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle
  • Yeah those job hoppers are the worst. You can always tell right away what kind of person those are. I’ve had to work with a “senior” dev who had 15 years of experience and to be honest he sucked at his job. He couldn’t do simple tasks, didn’t think before he started writing code and often got stuck asking other people for help. But he got paid big bucks, because all he did his entire career was work somewhere for 2-3 years and then job hop and trade up. By the time the company figured out the dude was useless, he went on to the next company.

    Such a shitty attitude, which is a shame because he was a good dude otherwise. I got along with him on a personal level. And honestly good on him for making the most he can, fuck the company. But I personally couldn’t do that, I take pride in my work.


  • Agreed. I wanted to test a new config in my router yesterday, which is configured using scripts. So I thought it would be a good idea for ChatGPT to figure it out for me, instead of 3 hours of me reading documentation and trying tutorials. It was a test scenario, so I thought it might do well.

    It did not do well at all. The scripts were mostly correct but often in the wrong order (referencing a thing before actually defining it). Sometimes the syntax would be totally wrong and it kept mixing version 6 syntax with version 7 syntax (I’m on 7). It will also make mistakes and when I point out the mistake it says Oh you are totally right, I made a mistake. Then goes on to explain what mistake it did and output new code. However more often than not the new code contained the exact same mistake. This is probably because of a lack of training data, where it is referencing only one example and that example just had a mistake in it.

    In the end I gave up on ChatGPT, searched for my testscenario and it turned out a friendly dude on a forum put together a tutorial. So I followed that and it almost worked right away. A couple of minutes of tweaking and testing and I got it working.

    I’m afraid for a future where forums and such don’t exist and sources like Reddit get fucked and nuked. In an AI driven world the incentive for creating new original content is way lower. So when AI doesn’t know the answer, you are just hooped and have to re-invent the wheel yourself. In the long run this will destroy productivity and not give the gains people are hoping for at the moment.


  • Me and my brother once bought one of those Steam key mystery packs, it was only a few bucks and we did it for shits and giggles. The deal was we should each choose one of those games for the other and play them and at least seriously attempt to beat it if possible. The description said it included x amount of games with a value of at least x amount of dollars.

    Turns out half of them were abandoned early-access games. Still for sale for way too much money. One of them was 49.99, which made the key bundle indeed be worth a lot. However the game was just an old Unreal project with some stock assets from the asset store. There wasn’t even a game really and it kept crashing. Last updated 4 years ago.

    Really disappointing, we thought we would have some fun with unknown terrible games. But we didn’t expect them to be literally not a game. So instead we played Bad Way, a really fun but seriously flawed game. We had a blast.








  • I’ve seen this often. The app is marketed as being “api” first as if that’s some benefit to the user of a SaaS application. However in reality much of the team is constantly busy patching the old legacy V1 api to keep it running. And management won’t authorize the budget to create a new api version that replaces the old one, because it still works right?

    Public facing web apis have always been a pet peeve of mine. So often the team uses the api their own frontend uses as the public facing api customers should use for integrations. Which on the surface seems smart, why implement and manage two apis that’s just overhead. But in reality the apis suitable for a frontend (or often that specific frontend) isn’t suitable for integrations at all. They both have a completely different target user and completely different requirements.

    But hey we’ll just market it as “headless”, because one could totally put in the years of work and money we put in to create our front-end, if they really wanted to. Totally realistic thing that happens.




  • To add to this good info: In the post is a screenshot showing the SPF/DKIM/DMARC info on the mail, it all checks out. So even if you are tech savvy and actually check these things, in this case they got it licked.

    This is what elevates this attack from every day regular attack to holy shit I could have fallen for that.






  • Because when the Apollo project was ongoing, they only built what they needed to build. Everything was a prototype basically and there were usually different versions of everything going around. Afterwards a lot of the stuff was re-used for later programs, often modified or taken apart for parts. As the budget shrank they needed to be creative. Take a look at the work CuriousMarc and his team is doing with repairing and restoring old Apollo Moon hardware, along with documentation and preservation.

    Why can’t we simply build the Apollo lander today. Well a couple of reasons.

    First of all, like I said it were prototypes, so you’d have to figure out what design to use. All of the documents back then were on paper and not all of it is digitized by a long shot. The amount of documents they produced back then was crazy. And a lot of it was lost over time unfortunately. Puzzling all of that together would be quite some task. Most folk from back then are since dead or at the very least retired. And I for one sometimes forget entire projects I worked on, so good luck getting small details out of those people.

    Our idea of what is acceptable, a good idea and safe has changed since the Apollo times. A lot of the design back then included components that were very dangerous and toxic. Not only to be used, but also to manufacture, which we wouldn’t find acceptable these days. And things we’ve later learned were a bad thing to do. So the design would need to be modified to be safer, which would probably cascade into an entire new design.

    We’ve lost so much of the support infrastructure the program relied on. It’s hard to understate how much this matters. This is a big thing when people say the moon program was fake. It wasn’t just one rocket, one lander, one crew, it was millions upon millions of pieces of infrastructure supporting the whole thing. From jigs to electronics, test equipment, custom tools, handling facilities etc. All with their own backstory, design requirements, documentation etc. A lot of this has been lost, especially when it was outsourced at the time. You’d have to reverse engineer and re-create a lot of that.

    Time has moved on and so has technology. Whilst the Apollo program had some cutting edge stuff back then, these days it’s ridiculously outdated. It would be very hard to manufacture any of those components today. We’re talking about the first generation of integrated circuits, on very expensive ceramics. Using crazy analogue electronics, only understood by the best gurus at the time. Even mechanical computers were used, a lost artform last used in the 80s. You could start redesigning stuff to modern equivalents, but again that would probably snowball into just designing a whole new thing.

    Recreating something from that long ago is simply not possible I’m afraid. And even if we could, it would probably make for a pretty shitty lander compared to modern standards.


  • Well it all depends on what you want to do. I interpreted your question as we need to go there asap, what can we do? And then the answer is we can do an crewed orbit in about a year time.

    If we just want to do it with a good chance of survival, building all the shit we need, but still get there soon, the answer would be different. If we just want to go fast, we would probably use all our heavy lift vehicles to build a moon vehicle in LEO. Then put a big ass engine on that and a bunch of fuel and launch the whole thing to the moon. That’s something we could do within 5-7 years if we would put our minds and money to it. I feel the suits we currently have in development could be ready within that time as well. The lander would be a problem however, we don’t have any of those in development right now. Blue Origin has their Blue Lander, but that’s been on the drawing board for so long now. They did get extra funding to get it ready for 2030, but haven’t shown their progress publicly, so who knows how far they are. On the other hand, if we want to take some risks for this special mission I’m sure we can get something together in 5-7 years if humanity unites and puts their weight/money/faith behind it.

    However if we keep going like we’ve been going since Apollo was cancelled, we are never going to get there at all. The politics are complicated and the private sector has been hit or miss. Plus with the Musk factor, we don’t know what’s going to happen. I have zero faith in anything we have going right now.


  • Thorry84@feddit.nltoTechnology@lemmy.worldArtemis II plan (April, 2026)
    link
    fedilink
    English
    arrow-up
    21
    arrow-down
    1
    ·
    edit-2
    1 month ago

    At the moment, we just cannot.

    We don’t even have space suits that can operate on the moon. The stuff they use on the ISS is made to be used in a total vacuum only, not walking around in the dust and on sharp rocks. There are new suits in development, but nothing final as far as I know. I’m not sure if any are close to being finished, let alone tested and certified.

    There’s also no vehicle that can land on the moon with crew right now. Nasa is relying on SpaceX to get their Starship program to the point they can do it. People are divided on this, but anyone with technical knowledge I heard about this say the SpaceX program is very challenging and probably not feasible. Especially with the super optimistic timelines they’ve been throwing around.

    In theory you could put a Crew Dragon with a big trunk of supplies on a Falcon Heavy, which has the delta-V to go to the moon. But obviously that’s pretty risky, once you go you’re committed. When working in LEO you almost always have some kind of disaster recover scenario available where you abort and get back to earth asap. If you are underway to the moon, there is no turning back. The Crew Dragon has very limited mobility. But I think a trans-lunar injection and orbit around the moon would be possible, with a free return trajectory. So if going around the moon is good enough, that would be possible.

    Still it would probably take 9-12 months to put such a mission together and it would be very risky indeed. And like I said, landing on the moon is a total no-go right now.

    We should ask Scott Manley to do a video about this, I would love to hear his thoughts on this.