rob2d

583 posts

rob2d banner
rob2d

rob2d

@rob2d_u8

software engineer | builder | retro games | AI sans overhype

Universe 8 Katılım Ocak 2022
48 Takip Edilen103 Takipçiler
Sabitlenmiş Tweet
rob2d
rob2d@rob2d_u8·
Recently edited a long overdue vlog for a Dreamcast texture editor app. This was a special episode showcasing the work done on an CVS2 Dreamcast translation project led by @DerekPascarella & am very proud of being able to contribute w the gfx conversions. V1.1 coming soon.
English
3
3
22
1.6K
rob2d
rob2d@rob2d_u8·
@AlexBeyman @ManletThorin that would be wrong :) You got 61 because of SGDK, but it's 64 since SGDK always reserved 1 transparent for each palette, and that is 64 in only for the CRAM at any one time. You can just change CRAM on the fly mid frame. There is also shadow+highlight mode as well simultaneously
English
0
0
0
6
Alex Beyman
Alex Beyman@AlexBeyman·
The total palette |= simultaneous onscreen colors, which was 256 on SNES. 51 was a typo, of 61. Of the Sega Genesis' 64 simultaneous onscreen colors, 3 were different shades of light/dark iirc. There was the alternating palette per line trick to double onscreen colors only Eternal Champions use it iirc (and Toy Story cutscenes? I think?)
English
1
0
0
17
Manlet Thorin
Manlet Thorin@ManletThorin·
Sega Genesis games were on some shit with creature designs
Manlet Thorin tweet mediaManlet Thorin tweet mediaManlet Thorin tweet mediaManlet Thorin tweet media
English
107
594
5.7K
157.3K
rob2d
rob2d@rob2d_u8·
@AlexBeyman @ManletThorin Not sure what you mean 👀 Genesis had 512 colors, and 4 palettes w 60-64 colors depending on if there's alpha + there were tricks to get a lot more.
English
1
0
0
25
Alex Beyman
Alex Beyman@AlexBeyman·
@ManletThorin 51 colors is rough though. I love Sega but 256 on SNES aged far better. Even TurboGrafX had more
English
1
0
0
399
rob2d
rob2d@rob2d_u8·
@Boson_Zhe @Grady_Booch That just means it wasn't a great place imo. It was never hard to do any of this. If having more slop means less tech debt cause of apathy then that is another problem entirely.
English
0
0
0
9
Evgenii
Evgenii@Boson_Zhe·
@rob2d_u8 @Grady_Booch Yet in some companies sheer fear of moving / changing things was obvious until some LLM was around to help folks move shit to cloud / make builds more transparent / etc; was a witness of this. LLM is about catching up for non tech savvy biz for which tech debt has been piling up
English
1
0
0
12
Grady Booch
Grady Booch@Grady_Booch·
Having been part of the industry for 50 years, I can confidently report that none of this is true. Sure, writing code has a non-zero cost; this is true of any artifact. But you know what costs even more, Jonathan? Writing bad code; writing unnecessary code; writing more code than you really need simply because you think you might need it someday or you are too lazy or sloppy to clean up after yourself. Anything that costs nothing is often worth nothing as well, and results in significant unintended consequences.
Jonathan Ross@JonathanRoss321

For 50 years, software engineering ran on code rationing. Writing code was expensive, so we rationed it carefully through roadmaps, RFCs, prioritization meetings, and scope reviews. This created a role: the No Engineer. No, that won't scale. No, we don't have bandwidth. No, that's out of scope. No, we need a design doc first. The No Engineer was valuable for 50 years. Every "no" saved real money. Their judgment was the rationing system. LLMs will be the end of code rationing. Code is cheap now. And while the No Engineer is explaining why something can't be done, the Yes Engineer has already shipped three versions of it. If you're a Yes Engineer, the next decade is yours.

English
87
240
2.3K
131K
rob2d
rob2d@rob2d_u8·
@ThePrimeagen @thdxr I can't imagine the average of 2026. I'm glad I don't have to and work with people that need things to feel good.
English
0
0
0
18
ThePrimeagen
ThePrimeagen@ThePrimeagen·
@thdxr I honestly cannot even imagine what a 2027 codebase will look like
English
39
2
342
15.7K
dax
dax@thdxr·
1 year old codebase is the new 5 year old codebase
English
61
30
1.3K
51.2K
rob2d
rob2d@rob2d_u8·
@rolandbouman @samwightt @rgb53562 *someone creating a compiler that works, creates efficient code, not bloated af and is pleasant to use. Not like the one for marketing vibe shitted out by Anthropic.
English
0
0
0
14
rob2d
rob2d@rob2d_u8·
@rolandbouman @samwightt @rgb53562 But why does using an LLM mean a human doesn't review it? If we're not talking about binary, then it should really be the norm that a human reviews everything unless the functionality actually doesn't matter at all. Someone creating a compiler by hand does the same.
English
2
0
0
25
rob2d
rob2d@rob2d_u8·
@shikhr_ No absolutely not lol. If you want to be an SWE you will not get there by vibe slopping like it's bird cage. You need to be able to review code more than ever.
English
0
0
1
28
Shikhar
Shikhar@shikhr_·
Is learning the syntax of programming languages a depreciating skill now?
English
32
0
30
2.7K
rob2d
rob2d@rob2d_u8·
@rolandbouman @samwightt @rgb53562 Granted there are differences but the description you're giving is obscuring the actual abstraction for what an LLM is used for with code gen. If it's a statistical interpreter and you aren't giving it the right quantity/medium/quality of context then that is a different issue.
English
0
0
0
7
rob2d
rob2d@rob2d_u8·
@rolandbouman @samwightt @rgb53562 If the output is wrong that often you should learn to use the tech a bit better; it generally is as accurate as spec. Otherwise we're conflating the responsibility of a dev as not to review or give good direction. Same as jr devs or a hll.
English
2
0
0
18
rob2d
rob2d@rob2d_u8·
@TheRabbitPy @CodeEdison If you ask better questions you might not be vibe coding or coding for $ to begin with. For dev, need to be a person with attention to detail at different granularity if you want to stay employed. Otherwise everyone's vibe slop is interchangeably unreliable no matter what Qs
English
0
0
1
12
Edison
Edison@CodeEdison·
If AI writes 80% of code, who even survives in tech?
English
40
0
43
9.2K
rob2d
rob2d@rob2d_u8·
@CodeEdison The people who review it and architect and think properly. Technically everyone survived but at least the people who don't get fired for things outside of unavoidable corporate stupidity.
English
0
0
0
274
rob2d
rob2d@rob2d_u8·
@samwightt @rgb53562 @rolandbouman Not actually the case. There were a lot of compiler bugs that plagued C compilers for many years, and most new compiles have them. They are more rare but can be even more terrible :) (though LLM goes only as far as the user's senses and engineering discipline)
English
1
0
0
21
Sam
Sam@samwightt·
@rgb53562 @rolandbouman Compilers were also never 'unreliable'. They produced unoptimized code sure, but they almost always produced *correct* unoptimized code. That is not the case with LLMs.
English
3
0
0
114
rob2d
rob2d@rob2d_u8·
@bazzilic @rgb53562 @rolandbouman I'm not a fan of vibe coding and I was also wondering the same thing. Compiler output in ASM is much more taxing to do this with (I have done both and have written a lot of ASM at various times)
English
0
0
0
20
rob2d
rob2d@rob2d_u8·
@rgb53562 @rolandbouman Uhh.. you can actually do this with an LLM, much easier than with assembly. It should be more the norm tbf. If you can't describe what you're coming in English or trying to one shot Ralph loops otoh you cannot. That is not in fact what most swe do at work, more hobbyists.
English
1
0
0
21
rgb
rgb@rgb53562·
@rolandbouman In the early days when compilers were still unreliable, people actually looked at the assembly. Any bugs were reported to the compiler maker. And so the errors were slowly expunged, and reliability was achieved. Not something you can really do with LLMs.
English
5
1
124
3.3K
rob2d
rob2d@rob2d_u8·
@JoshuaJAlbert @loftwah And you would be correct sir! A lot of devs casually, and some popular apis incorrectly call a `dir` a path ``` dir = "/home/user/projects" os.chdir(dir) # "dir" here is actually a path ``` I don't care enough not to like it, but that was the only reason I commented w all 3
English
0
0
1
13
Joshua J Albert
Joshua J Albert@JoshuaJAlbert·
@rob2d_u8 @loftwah Path? Oooh, I don't like that. A folder (or directory) *has* a path, just like it has a name. You can't call a folder a "path". Its not right.
GIF
English
1
0
1
9
Loftwah
Loftwah@loftwah·
As a developer, do you call it a folder or a directory?
English
127
0
63
14.6K
rob2d
rob2d@rob2d_u8·
@atatarynstudio @SahilBlueSky @vivoplt And you will need a professional who knows what their doing to do it better, since it shouldn't get there to begin with when building with AI properly either.
English
1
0
1
15
Vivo
Vivo@vivoplt·
Software Engineers, what’s your plan B if Artificial Intelligence writes better code than you in next 6 months?
English
280
11
303
61.8K
Clifford Richardson
Clifford Richardson@CorvusCrypto·
@lochan_twt People are too focused imo on AI coding or not. The process that should drive your company are the ones that achieve the goals you have with quality, speed, and cost all balanced. Some companies will not benefit from AI code generation because the bottleneck lies elsewhere.
English
2
0
4
1.3K
spidey
spidey@lochan_twt·
the knowledge gap between software engineers right now is insanely wide some devs are writing every single line of code by hand, understanding evey single thing others are shipping everything using AI, by just prompting and bearly touching the code who do you think will win ??
English
99
10
517
83.8K
Sahil Purav
Sahil Purav@SystematicSahil·
@vivoplt Plan B? We will be the “Professional Janitor” charging 3x to clean up the architectural debt left behind by “Vibe Coders” who didn't realize that production doesn't care about vibes 😁
English
4
0
10
586

Keşfet

@AlexBeyman @ManletThorin @Boson_Zhe @Grady_Booch @ThePrimeagen @thdxr @rolandbouman @samwightt