Loading video...

Video Failed to Load

Go Home

** Sega Genesis 3D Engine Day 3 ** Blast Processing kicks In !! Converted the Line Drawing and Triangle drawing to 68k Assembly and gained 25% in the line drawing and 33% speedups in the triangle drawing vs C ( so far ) . The scheduler calculating the vertexs...

birt_shannon's profile picture

Shannon Birt

2,505 subscribers

20,808 views • 3 months ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

** Sega Genesis 3D engine update 4 ** Never can leave a good rabbit hole undug ! .. updates since last update : Changed frame buffer from a VDP tile friendly buffer to a linear buffer which needs CPU translation , which speedup drawing a LOT not having to worry about tile boundaries albiet slows buffer sending to VRAM. The interior filling of triangles now is running at 1.5c ( 68k cycles ) per pixel ! however sending the buffer is twice as slow per byte as we need the CPU to send the buffer to VRAM to write to the tile format the VDP needs, rather than DMA directly to VRAM . Overall speedup 25% + as the drawing speedup is much greater than the frame buffer slow down. Optimised Line drawing and Triangle filling -near optimal now for the linear frame buffer. Triangle drawing might get a little bit more yet. Quad drawing is next on the list as that will speedup drawing quads. Some gains will come from been smart about partial clearing of RAM buffers and partial sending to VRAM buffers, rather than send the whole buffer. Vertice rotation and projection needs a lot of optimising .. i expect good gains to come from this - this is all in C at present and all calced in real time. Line and Triangle drawing are in assembly but all vertex manipulation is in C. #SGDK #MegaDrive #SegaGenesis
0:24

** Sega Genesis 3D engine update 4 ** Never can leave a good rabbit hole undug ! .. updates since last update : Changed frame buffer from a VDP tile friendly buffer to a linear buffer which needs CPU translation , which speedup drawing a LOT not having to worry about tile boundaries albiet slows buffer sending to VRAM. The interior filling of triangles now is running at 1.5c ( 68k cycles ) per pixel ! however sending the buffer is twice as slow per byte as we need the CPU to send the buffer to VRAM to write to the tile format the VDP needs, rather than DMA directly to VRAM . Overall speedup 25% + as the drawing speedup is much greater than the frame buffer slow down. Optimised Line drawing and Triangle filling -near optimal now for the linear frame buffer. Triangle drawing might get a little bit more yet. Quad drawing is next on the list as that will speedup drawing quads. Some gains will come from been smart about partial clearing of RAM buffers and partial sending to VRAM buffers, rather than send the whole buffer. Vertice rotation and projection needs a lot of optimising .. i expect good gains to come from this - this is all in C at present and all calced in real time. Line and Triangle drawing are in assembly but all vertex manipulation is in C. #SGDK #MegaDrive #SegaGenesis

Shannon Birt

15,134 views • 2 months ago

** Sega Genesis 3D engine Day 2 ** Added solid filled triangles. Added colors ( full 15 color buffer ) . All code in C so far apart form the buffer clear and DMA buffer sending so should be some good speedups to come yet once line / triangle routines are ported to 68k Assembly. I've done basic filling optimisations in C such as where we can write longs eg fill 8 pixels at once for interior parts of the triangle the function will utilise that. Still using 3 divisions per triangle setup , I think i will see if I can use a cheaper reciprical multiplication instead. All rotations vertices are calculated live , in 2d space at present. #SGDK #SegaGenesis #SegaMegadrive
0:26

** Sega Genesis 3D engine Day 2 ** Added solid filled triangles. Added colors ( full 15 color buffer ) . All code in C so far apart form the buffer clear and DMA buffer sending so should be some good speedups to come yet once line / triangle routines are ported to 68k Assembly. I've done basic filling optimisations in C such as where we can write longs eg fill 8 pixels at once for interior parts of the triangle the function will utilise that. Still using 3 divisions per triangle setup , I think i will see if I can use a cheaper reciprical multiplication instead. All rotations vertices are calculated live , in 2d space at present. #SGDK #SegaGenesis #SegaMegadrive

Shannon Birt

17,379 views • 3 months ago

** Sega MD 3D engine update 7 ** Speed up rendering by another 15-20 % ! Massive unrolling of the line drawing hotpath has seen a good pickup in the rendering although further improvements are needed , particularly for small triangles as most of the overhead is not in the drawing ( more time in setup vs drawing ) . Added partial drawing of Quads , this was a major pain due to all the edge cases , as Quads are basically a triangle top (optional) - a middle trapezium and a bottom triangle (optional) and any part can be clipped or offscreen . Implemented a frame pacing algorithm for the camera so as Frame rate fluctuates with detail the forward Z rate is altered, its as bit janky still . Track control just snaps back to position after it runs through a short sequence. Work continues on Parodius and we have some cool things to show in a video soon . #SGDK #SegaGenesis #MegaDrive
0:24

** Sega MD 3D engine update 7 ** Speed up rendering by another 15-20 % ! Massive unrolling of the line drawing hotpath has seen a good pickup in the rendering although further improvements are needed , particularly for small triangles as most of the overhead is not in the drawing ( more time in setup vs drawing ) . Added partial drawing of Quads , this was a major pain due to all the edge cases , as Quads are basically a triangle top (optional) - a middle trapezium and a bottom triangle (optional) and any part can be clipped or offscreen . Implemented a frame pacing algorithm for the camera so as Frame rate fluctuates with detail the forward Z rate is altered, its as bit janky still . Track control just snaps back to position after it runs through a short sequence. Work continues on Parodius and we have some cool things to show in a video soon . #SGDK #SegaGenesis #MegaDrive

Shannon Birt

17,658 views • 2 months ago

Most C Programmers don't have a clue as to how the CPU works. Here is a lecture from my course on the C Language that introduces how to visualise the CPU as a C (or general software) Programmer.... More Details are at: Being able to model the behaviour of CPU provides a solid base to reason about your code. The summary is - - The CPU is a state machine which maintains it's states in registers. - It has busses to memory for requesting data/instruction read/writes. - Interrupts to attend to events. I discuss this and more in my course on the C Language.
11:41

Most C Programmers don't have a clue as to how the CPU works. Here is a lecture from my course on the C Language that introduces how to visualise the CPU as a C (or general software) Programmer.... More Details are at: Being able to model the behaviour of CPU provides a solid base to reason about your code. The summary is - - The CPU is a state machine which maintains it's states in registers. - It has busses to memory for requesting data/instruction read/writes. - Interrupts to attend to events. I discuss this and more in my course on the C Language.

Piyush Itankar

28,019 views • 1 year ago

** MEGA Parodius Scaling Effects Part 1 ** One of the big challenges with the Parodius Megadrive port is Stage 8's boss - The puffer-fish *Pooyan* with his full screen scaling effect. The goal is to be very close to the arcade (with extras on top ) so I thought lets tackle it head on to see how close we can get. I was also keen to jump into another scaling code rabit hole haha. Pyron pulled out all the stops and got me the source frames and reworked the BG tiles for this test - a big thankyou to him , Vector Orbitex is busy working on Stage 2 tracks so the team is working hard all round on this port. The MD has no sprite / background GFX scaling hardware , however the VDPs Vertical scroll can be updated per scanline to help vertical scaling on backgrounds, but there is a cpu cost to manage all the interupts so thats not free either. With the Horizontal scaling there is no help at all , apart from a semi-friendly packed pixel format for the cpu to work with, its not quite chunky format but better than planar format still for scaling. So its falls back to the 68k CPU to do all of the horizontal expansion which is the largest cpu cost. Basically drawing strips of either 1x, 2x, 3x or 4x wide columns at speed. So we are one week into this Boss's routine and you can see from the below video the horizontal scaling is implented ( vertical will be in the next update ) . We are scaling from 1x to 4x in the video below in 74 steps for testing . The column distributions are always a bit painfull to do - thankfully they are all worked out now. This is the third scaler I have built and the goal was with this one to make it really flexible for use in other projects also, sometimes when you optimise something to the last degree all the flexibility gets taken out of it. Currenty scaling at 12-25 FPS update here, I had some rules against some optimisations which I would use and some I wouldn't , thankfully we are a bit ahead of the Arcades animation frame rate here still and I may yet find optimisations that fit within the scope. We have vertical scaling and sprite spikes to add yet so Im hoping i can find a few more optimisations to offset things when they are implemented also. In a scale frame update we are processing close to 42000 pixels in ram before using DMA to send to VRAM . Using a 41x16 (656 tile scale buffer) - single buffered for now due to its size in VRAM. So thats nearly 21k in tiles ! I had to re-organise ram a bit to support a buffer of that size for the stage. The scaling function is written in 68k assembly , with a little C code handling the Vertical interupt code ( so the game logic can actually run & DMA updates etc ) . The DMA routines are in assembly also and customised for large chunk size ( big blocks of tiles ) which suits the scaler. I had some race conditions to sort out where the cpu was faster than DMA (sending tiles from RAM to VRAM ) and in some cases where it wasn't so it had to be balanced. We may be able to add more detail into the top and bottom of the background yet but its low priority for now until all the other bits are in !! #SGDK #SegaMegadrive #Genesis #Parodius
0:30

** MEGA Parodius Scaling Effects Part 1 ** One of the big challenges with the Parodius Megadrive port is Stage 8's boss - The puffer-fish *Pooyan* with his full screen scaling effect. The goal is to be very close to the arcade (with extras on top ) so I thought lets tackle it head on to see how close we can get. I was also keen to jump into another scaling code rabit hole haha. Pyron pulled out all the stops and got me the source frames and reworked the BG tiles for this test - a big thankyou to him , Vector Orbitex is busy working on Stage 2 tracks so the team is working hard all round on this port. The MD has no sprite / background GFX scaling hardware , however the VDPs Vertical scroll can be updated per scanline to help vertical scaling on backgrounds, but there is a cpu cost to manage all the interupts so thats not free either. With the Horizontal scaling there is no help at all , apart from a semi-friendly packed pixel format for the cpu to work with, its not quite chunky format but better than planar format still for scaling. So its falls back to the 68k CPU to do all of the horizontal expansion which is the largest cpu cost. Basically drawing strips of either 1x, 2x, 3x or 4x wide columns at speed. So we are one week into this Boss's routine and you can see from the below video the horizontal scaling is implented ( vertical will be in the next update ) . We are scaling from 1x to 4x in the video below in 74 steps for testing . The column distributions are always a bit painfull to do - thankfully they are all worked out now. This is the third scaler I have built and the goal was with this one to make it really flexible for use in other projects also, sometimes when you optimise something to the last degree all the flexibility gets taken out of it. Currenty scaling at 12-25 FPS update here, I had some rules against some optimisations which I would use and some I wouldn't , thankfully we are a bit ahead of the Arcades animation frame rate here still and I may yet find optimisations that fit within the scope. We have vertical scaling and sprite spikes to add yet so Im hoping i can find a few more optimisations to offset things when they are implemented also. In a scale frame update we are processing close to 42000 pixels in ram before using DMA to send to VRAM . Using a 41x16 (656 tile scale buffer) - single buffered for now due to its size in VRAM. So thats nearly 21k in tiles ! I had to re-organise ram a bit to support a buffer of that size for the stage. The scaling function is written in 68k assembly , with a little C code handling the Vertical interupt code ( so the game logic can actually run & DMA updates etc ) . The DMA routines are in assembly also and customised for large chunk size ( big blocks of tiles ) which suits the scaler. I had some race conditions to sort out where the cpu was faster than DMA (sending tiles from RAM to VRAM ) and in some cases where it wasn't so it had to be balanced. We may be able to add more detail into the top and bottom of the background yet but its low priority for now until all the other bits are in !! #SGDK #SegaMegadrive #Genesis #Parodius

Shannon Birt

25,545 views • 5 months ago

I was playing around with my scaling code and thought it would be cool to play the current Lufthoheit service screen on a CRT on the tripple bypassed MD2 i got recently. I've made the code a bit more efficient and added a whole scale factor so now it scales 320 pixels wide x 4 times ( source art width ) . So the ship here is scaled 4x larger than the one we scale at the entrance to the cave level . I'm working on 5x next . Scaler and Rotater are written in 68k assembly for speed . Finally I got the non-safe interupts (eg register allocation / seperation ) to work which yielded a big speed gain . Basically you reserve some of the 68ks registers only for use in the Horizontal Interupts (hints) and other code outside the Hints must not use them during the Hints that are occuring every line. The Hints are doing the vertical scaling work . Its a bit tricky to syncronise and protect but finally it worked. The MDs VDP is scaling vertically (its still not free) , the 68k cpu is scaling the ship horizontally . The 68k does the asteroid rotation . #SegaGenesis #SegaMegadrive CYBERDEOUS - Crouzet Laurent Carsten666
0:42

I was playing around with my scaling code and thought it would be cool to play the current Lufthoheit service screen on a CRT on the tripple bypassed MD2 i got recently. I've made the code a bit more efficient and added a whole scale factor so now it scales 320 pixels wide x 4 times ( source art width ) . So the ship here is scaled 4x larger than the one we scale at the entrance to the cave level . I'm working on 5x next . Scaler and Rotater are written in 68k assembly for speed . Finally I got the non-safe interupts (eg register allocation / seperation ) to work which yielded a big speed gain . Basically you reserve some of the 68ks registers only for use in the Horizontal Interupts (hints) and other code outside the Hints must not use them during the Hints that are occuring every line. The Hints are doing the vertical scaling work . Its a bit tricky to syncronise and protect but finally it worked. The MDs VDP is scaling vertically (its still not free) , the 68k cpu is scaling the ship horizontally . The 68k does the asteroid rotation . #SegaGenesis #SegaMegadrive CYBERDEOUS - Crouzet Laurent Carsten666

Shannon Birt

11,606 views • 11 months ago

*** Mega Parodius Sega Megadrive Update *** Lately I've been having some fun seeing how far we can push the Parodius game engine . This is not arcade accurate - just for testing, decreased bullet timers and upped the bullet count to see what would happen re cpu usage when things are made a lot busier ! Maybe something like this could be insane mode in the options etc. Since last update we are a lot more optimised under the hood . The C based sprite engine, particularly visibility checking was speedup , overall 25 % faster. Then re-wrote the sprite engine completely in 68k assembly , 30% faster again. It took about 3 days and 1500 lines of assembly , thankfully the gains were worth it. All these gains will be back ported to S.O.T.A also as its using the same sprite engine. Usage is around 19% of cpu per frame with a full sprite load - 33 % cpu left in the busiest frame currently . Parodius is using a write the sprite list every frame type engine , so priority and meta-sprite objects can be handled with ease albiet its still a bit slower than static allocation sprite engines such as the one in lufthoheit but this is a bit easier to code for in the long run. All collision checks are been done , we are using a spatial grid system to get the collision checks done faster than a brute force approach . To get to maximum sprite count destruction is disabled in the video. We hit 80 sprites onscreen in this sequence , the sprite counter is one the Left side. We use about 16 sprites in the top hud and water line , about 21 for player attacks / missiles / shots / options . Up to 35 bullets + enemies . No lazer usage here as the Lazers use zero sprites thanks to the raster tricks , this video is all about the sprites ! Improved the water line when the Catboss is active , as he is Sprites + Forground we are doing some tile rotation tricks eg bit scrolling to give the impression of parrallax at that point . Vector Orbitex has updated the stage 1 music again and has made things even higher quality , hes mixed pcm and fm channels together to create higher quality orchestral hits for example . Pyron has started converting assets from stage 2/3 , some amazing work there . Hes well ahead of me at present which is a good thing. Still lots of incomplete animations missing logic etc , its slow going with RL getting in the way haha and 2 other projects !! Still its fun !! #SGDK #SegaMegadrive #SegaGenesis #Parodius
0:41

*** Mega Parodius Sega Megadrive Update *** Lately I've been having some fun seeing how far we can push the Parodius game engine . This is not arcade accurate - just for testing, decreased bullet timers and upped the bullet count to see what would happen re cpu usage when things are made a lot busier ! Maybe something like this could be insane mode in the options etc. Since last update we are a lot more optimised under the hood . The C based sprite engine, particularly visibility checking was speedup , overall 25 % faster. Then re-wrote the sprite engine completely in 68k assembly , 30% faster again. It took about 3 days and 1500 lines of assembly , thankfully the gains were worth it. All these gains will be back ported to S.O.T.A also as its using the same sprite engine. Usage is around 19% of cpu per frame with a full sprite load - 33 % cpu left in the busiest frame currently . Parodius is using a write the sprite list every frame type engine , so priority and meta-sprite objects can be handled with ease albiet its still a bit slower than static allocation sprite engines such as the one in lufthoheit but this is a bit easier to code for in the long run. All collision checks are been done , we are using a spatial grid system to get the collision checks done faster than a brute force approach . To get to maximum sprite count destruction is disabled in the video. We hit 80 sprites onscreen in this sequence , the sprite counter is one the Left side. We use about 16 sprites in the top hud and water line , about 21 for player attacks / missiles / shots / options . Up to 35 bullets + enemies . No lazer usage here as the Lazers use zero sprites thanks to the raster tricks , this video is all about the sprites ! Improved the water line when the Catboss is active , as he is Sprites + Forground we are doing some tile rotation tricks eg bit scrolling to give the impression of parrallax at that point . Vector Orbitex has updated the stage 1 music again and has made things even higher quality , hes mixed pcm and fm channels together to create higher quality orchestral hits for example . Pyron has started converting assets from stage 2/3 , some amazing work there . Hes well ahead of me at present which is a good thing. Still lots of incomplete animations missing logic etc , its slow going with RL getting in the way haha and 2 other projects !! Still its fun !! #SGDK #SegaMegadrive #SegaGenesis #Parodius

Shannon Birt

16,084 views • 7 months ago

** MEGA Parodius Scaling Effects Part 2 ** Well - this is the BIG one - literally !! Huge thanks to my team Pyron & Vector Orbitex for their efforts. Pyron has provided all the source frames for Puyon and his spikes / explosion and a lot of analysis video on how the spikes behave / move which was really helpful. Pyron also used his CRT setup for this video as we felt an emulator video would not do it justice - running on 100% real MD hardware FTW. Vector has provided the catchy boss music and its sounding great - as always ! The coding on this has been a bit insane - things done since part 1 post previous: Implemented dual buffering - Last video was single buffered - so VRAM is very tight now , we only have about 40/2048 tiles free. For the longest time I didn't think it would fit - I found a vram jigsaw puzzle that made it work in the end. Double buffering has cleaned up the stability of the animation and matches the arcade scaling effect now albiet costing 2x more VRAM . Vertical Scaling Implemented - the vertical scaler was taken from Lufthoheit ( my other shooter ) and its heavily optimised to reduce cpu usage. During the scaling the vertical scaler partitions the 68k processor registers into 2 sets, 4 registers are allocated to feeding the fast horizontal interrupt (h-int) that drives the vertical scaling , remaining 12 registers are for the horizontal scaler running in the background. This setup is much faster than normal backup / restore register methods, as we do not need to backup / restore registers in the h-int which would double CPU costs. The catch is the momment any background routine tries to use the H-ints registers it would break things so it has to be carefully timed. Added the spike projectiles - this was very tricky to get close to the arcade, they are semi heat seeking missiles basically and hence needed code that worked out angle differences to player at speed theres no time for arc-tan or similar so it uses faster lookup tables to work out the angles . They speed up over time and get larger and whats more we can't keep all the scales in VRAM - we have room for 2 spike buffers only. Also what was a real pain was working out scaled coordinates for the circular launch of the spikes . Added Fish Damage - Shock frame and Explosion frames from Arcade . Very proud of the fact we have the full arcade quality explosion is which is fully scaled also. Added Temporal Masking - which is fancy wording for don't draw nothing to buffer if nothing is there already there for the scaling . So empty Corners and edges can be optimised out to lower cpu costs and rom costs. I had to make some scripting for this and work out what areas did not need drawing at all in the frame, which should be force cleared by cpu and which areas should just be copied from rom. This reduced rom size by 30 kb and with a bit more work we could extend that to 60 kb & get a bit more speedup even doing so. Added a frame limiter . In the last video update we let the 68k burn hot and just pump out frames as fast as it could - here we match the arcade animation rate which does leave the cpu idling at times , particularly in the smaller frames - even at large though we could be running the animation 25 % faster , issue is though that would speed up the game logic and make it less arcade accurate. We had some real bullet / Spike hell simulations going without the limiter but yeah we had to tone it down a bit. Maybe in a hardcore mode we could let it run wild though ! Code is 95% 68k assembly with about 5% C code (v-int as its cold path ) driving things . This sort of thing needs all the speed it can get !! Well now after all that I can return to finish off Level 1 haha - just a wee sidetrack there . No doubt we will polish stage 8 boss some more in time too !! #SegaMegadrive #SegaGenesis #Parodius #SGDK
0:58

** MEGA Parodius Scaling Effects Part 2 ** Well - this is the BIG one - literally !! Huge thanks to my team Pyron & Vector Orbitex for their efforts. Pyron has provided all the source frames for Puyon and his spikes / explosion and a lot of analysis video on how the spikes behave / move which was really helpful. Pyron also used his CRT setup for this video as we felt an emulator video would not do it justice - running on 100% real MD hardware FTW. Vector has provided the catchy boss music and its sounding great - as always ! The coding on this has been a bit insane - things done since part 1 post previous: Implemented dual buffering - Last video was single buffered - so VRAM is very tight now , we only have about 40/2048 tiles free. For the longest time I didn't think it would fit - I found a vram jigsaw puzzle that made it work in the end. Double buffering has cleaned up the stability of the animation and matches the arcade scaling effect now albiet costing 2x more VRAM . Vertical Scaling Implemented - the vertical scaler was taken from Lufthoheit ( my other shooter ) and its heavily optimised to reduce cpu usage. During the scaling the vertical scaler partitions the 68k processor registers into 2 sets, 4 registers are allocated to feeding the fast horizontal interrupt (h-int) that drives the vertical scaling , remaining 12 registers are for the horizontal scaler running in the background. This setup is much faster than normal backup / restore register methods, as we do not need to backup / restore registers in the h-int which would double CPU costs. The catch is the momment any background routine tries to use the H-ints registers it would break things so it has to be carefully timed. Added the spike projectiles - this was very tricky to get close to the arcade, they are semi heat seeking missiles basically and hence needed code that worked out angle differences to player at speed theres no time for arc-tan or similar so it uses faster lookup tables to work out the angles . They speed up over time and get larger and whats more we can't keep all the scales in VRAM - we have room for 2 spike buffers only. Also what was a real pain was working out scaled coordinates for the circular launch of the spikes . Added Fish Damage - Shock frame and Explosion frames from Arcade . Very proud of the fact we have the full arcade quality explosion is which is fully scaled also. Added Temporal Masking - which is fancy wording for don't draw nothing to buffer if nothing is there already there for the scaling . So empty Corners and edges can be optimised out to lower cpu costs and rom costs. I had to make some scripting for this and work out what areas did not need drawing at all in the frame, which should be force cleared by cpu and which areas should just be copied from rom. This reduced rom size by 30 kb and with a bit more work we could extend that to 60 kb & get a bit more speedup even doing so. Added a frame limiter . In the last video update we let the 68k burn hot and just pump out frames as fast as it could - here we match the arcade animation rate which does leave the cpu idling at times , particularly in the smaller frames - even at large though we could be running the animation 25 % faster , issue is though that would speed up the game logic and make it less arcade accurate. We had some real bullet / Spike hell simulations going without the limiter but yeah we had to tone it down a bit. Maybe in a hardcore mode we could let it run wild though ! Code is 95% 68k assembly with about 5% C code (v-int as its cold path ) driving things . This sort of thing needs all the speed it can get !! Well now after all that I can return to finish off Level 1 haha - just a wee sidetrack there . No doubt we will polish stage 8 boss some more in time too !! #SegaMegadrive #SegaGenesis #Parodius #SGDK

Shannon Birt

26,424 views • 4 months ago

First time doing this, but hear me out 😂 The ball and Aasgaard both on the grass cut line. But in the official VAR line drawing he’s about a foot to a foot and a half ahead of that same line while his foot is planted on the ground?
0:20

First time doing this, but hear me out 😂 The ball and Aasgaard both on the grass cut line. But in the official VAR line drawing he’s about a foot to a foot and a half ahead of that same line while his foot is planted on the ground?

James

150,516 views • 3 months ago

Ported the #C64 sprite handler to to #SegaGenesis / #MegaDrive, #Amiga 500 and #SNES. The SNES seems to be slower than expected. Maybe we can blame the C compiler's code generator, but I'm not so sure...
0:27

Ported the #C64 sprite handler to to #SegaGenesis / #MegaDrive, #Amiga 500 and #SNES. The SNES seems to be slower than expected. Maybe we can blame the C compiler's code generator, but I'm not so sure...

Lazycow

10,173 views • 5 months ago

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."
2:04

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."

The Pragmatic Engineer

39,011 views • 1 month ago

*** SEGA GENESIS/MEGADRIVE - SCALING PART 2 *** Whats better on a Friday than seeing some scaling effects on the Megadrive ? .. nothing, so read on ... In the previous part we were software scaling in either axis by a given factor, but I couldn't change the scale factor per scanline on the same frame, so I couldn't skew the base image for tilting into screen eg Mode 7 type effects. - One issue was it was scaling column by column which got wrecked for performance trying per scanline adjustments. So I converted to a row scaler rather than column, this allowed expansions and contractions on a per scanline basis. - Speed up the code significantly , now running a sprite load + music + scaling on cpu with ~50% cpu free. Relied heavily on Python scripts I wrote to generate the 68k assembly for this as it was mind numbing labourious. In doing so I got the scripts competing with each other to come up with the fastest method for each scale , I'm starting to like python ;-) - Tried all sorts to speed up the horizontal interupt - handles vertical scaling, exotic methods eg unsafe interupts / racing the beam & updating the vertical scroll every X cpu cycles, in the end the Z80 cpu (audio) stealing the 68k cpu bus intermittendly just killed these ideas as it would only be 95% stable, ended up just doing smarter interupts that saved a lot of cpu instead. - The good and the bad, spent too long on this is the bad, the good is we will need it in Lufthoheit in a few places to make up for that !! Carsten666 CYBERDEOUS - Crouzet Laurent #SGDK #SegaMegadrive #SegaGenesis
0:25

*** SEGA GENESIS/MEGADRIVE - SCALING PART 2 *** Whats better on a Friday than seeing some scaling effects on the Megadrive ? .. nothing, so read on ... In the previous part we were software scaling in either axis by a given factor, but I couldn't change the scale factor per scanline on the same frame, so I couldn't skew the base image for tilting into screen eg Mode 7 type effects. - One issue was it was scaling column by column which got wrecked for performance trying per scanline adjustments. So I converted to a row scaler rather than column, this allowed expansions and contractions on a per scanline basis. - Speed up the code significantly , now running a sprite load + music + scaling on cpu with ~50% cpu free. Relied heavily on Python scripts I wrote to generate the 68k assembly for this as it was mind numbing labourious. In doing so I got the scripts competing with each other to come up with the fastest method for each scale , I'm starting to like python ;-) - Tried all sorts to speed up the horizontal interupt - handles vertical scaling, exotic methods eg unsafe interupts / racing the beam & updating the vertical scroll every X cpu cycles, in the end the Z80 cpu (audio) stealing the 68k cpu bus intermittendly just killed these ideas as it would only be 95% stable, ended up just doing smarter interupts that saved a lot of cpu instead. - The good and the bad, spent too long on this is the bad, the good is we will need it in Lufthoheit in a few places to make up for that !! Carsten666 CYBERDEOUS - Crouzet Laurent #SGDK #SegaMegadrive #SegaGenesis

Shannon Birt

11,070 views • 1 year ago

According to fick's law, the more moisture that's in your flower, the more water it will diffuse faster. This means that almost 80% of the water in your plants is gone in the first phase (constant rate)of drying, which, condition depending, can be the first 18 hours to ..🙄3 days according to *Challa 2020-KINETICS AND THE EFFECTS OF DRYING METHODS ON QUALITY OF (C*****s s****a L.) BUDS* Water adhesion principals state that with the surface moisture evaporated, water is less susceptible to the evaporative forces applied on it (falling rate). During this falling rate, your 60/60 is far less effective at pulling water than it was during the constant rate (which still wasn't ideal). Once we enter the second phase of drying, or the falling rate; dehydrated surface exposure, along with low water activation energy in that dehydrated flower means dramatically increased secondary metabolite oxidization. In effect, from this moment forward, that PSM count is going DOWN The longer we keep it on the rack, and not into cure, the faster this will happen In the study *(Basel). 2022- Postharvest Operations of C*****is and Their Effect on C****binòid Content: A Review, it was shown that significant secondary metabolite loss occurred at temperatures higher than 40°c . Below this number, the rate of degradation was relatively constant. As referenced in the above studies. The difference in secondary loss between drying at 71° vs. 77 or even 89° tends to be only 1–2 % with a net positive moisture loss, whereas time driven degradation over days to weeks can account for 30 % total loss or more. Meaning that temperature does affects secondary volatility, but the timing of drying matters WAYYYYY more So how am I drying these? Day 1 - 72°f 55% Day 2 - 72°f 55% Day 3 - 74°f 52% Day 4 - 75°f 50% Day 5 - 75°f 50% See the article on and citations. Share, repost, follow. Still not convinced? Google "sharkmouse drying" on Google and see what reddit has to say!
0:37

According to fick's law, the more moisture that's in your flower, the more water it will diffuse faster. This means that almost 80% of the water in your plants is gone in the first phase (constant rate)of drying, which, condition depending, can be the first 18 hours to ..🙄3 days according to *Challa 2020-KINETICS AND THE EFFECTS OF DRYING METHODS ON QUALITY OF (C*****s s****a L.) BUDS* Water adhesion principals state that with the surface moisture evaporated, water is less susceptible to the evaporative forces applied on it (falling rate). During this falling rate, your 60/60 is far less effective at pulling water than it was during the constant rate (which still wasn't ideal). Once we enter the second phase of drying, or the falling rate; dehydrated surface exposure, along with low water activation energy in that dehydrated flower means dramatically increased secondary metabolite oxidization. In effect, from this moment forward, that PSM count is going DOWN The longer we keep it on the rack, and not into cure, the faster this will happen In the study *(Basel). 2022- Postharvest Operations of C*****is and Their Effect on C****binòid Content: A Review, it was shown that significant secondary metabolite loss occurred at temperatures higher than 40°c . Below this number, the rate of degradation was relatively constant. As referenced in the above studies. The difference in secondary loss between drying at 71° vs. 77 or even 89° tends to be only 1–2 % with a net positive moisture loss, whereas time driven degradation over days to weeks can account for 30 % total loss or more. Meaning that temperature does affects secondary volatility, but the timing of drying matters WAYYYYY more So how am I drying these? Day 1 - 72°f 55% Day 2 - 72°f 55% Day 3 - 74°f 52% Day 4 - 75°f 50% Day 5 - 75°f 50% See the article on and citations. Share, repost, follow. Still not convinced? Google "sharkmouse drying" on Google and see what reddit has to say!

thatonesharkguy

18,262 views • 10 months ago

Don’t forget: every time to draw something, you improve by the tiniest fraction. And the longer you’ve been drawing, the smaller that fraction. But it’s still an improvement. And the longer you’ve been drawing, the faster you are. It compounds. You’ve got to remember that, or it’s too easy to lose motivation.
0:43

Don’t forget: every time to draw something, you improve by the tiniest fraction. And the longer you’ve been drawing, the smaller that fraction. But it’s still an improvement. And the longer you’ve been drawing, the faster you are. It compounds. You’ve got to remember that, or it’s too easy to lose motivation.

tomfoxdraws

11,705 views • 4 months ago

Math is art. Machine instructions are an abstraction derived from mathematical operations at the hardware level. Assembly is a low-level representation of these instructions. Your C code compiles down to assembly, and Python was implemented in C. Learn the math.
2:25

Math is art. Machine instructions are an abstraction derived from mathematical operations at the hardware level. Assembly is a low-level representation of these instructions. Your C code compiles down to assembly, and Python was implemented in C. Learn the math.

tetsuo

18,693 views • 1 year ago

.Secretary of War Pete Hegseth "I witnessed urgency. Right when we landed, another C-17 landed just minutes after us. Within 30 seconds of the aircraft coming to a full stop, a team on the ground pulled up, and the cargo was being unloaded. Wartime speed. To a man and to a woman—on the ground, in the air, on the flight line, in the TOC—I heard: we want everything faster. Higher op tempo. Wartime speed. The feeling was the exact opposite of the rotational units, year after year, in the wars in Iraq and Afghanistan that we are so familiar with. In those wars, it was always about the next rotation, never knowing when the mission would end or exactly what the mission was..."
1:03

.Secretary of War Pete Hegseth "I witnessed urgency. Right when we landed, another C-17 landed just minutes after us. Within 30 seconds of the aircraft coming to a full stop, a team on the ground pulled up, and the cargo was being unloaded. Wartime speed. To a man and to a woman—on the ground, in the air, on the flight line, in the TOC—I heard: we want everything faster. Higher op tempo. Wartime speed. The feeling was the exact opposite of the rotational units, year after year, in the wars in Iraq and Afghanistan that we are so familiar with. In those wars, it was always about the next rotation, never knowing when the mission would end or exactly what the mission was..."

DOW Rapid Response

102,291 views • 3 months ago

George 🗣️ “I had the steering problem again, from about lap 5 same as I had in quali, but I managed to drive around this and got used to the challenges of this problem. The pace looked quite good in stint 1 and then at the start of my 2 stint when Max came out of the pits I was like ‘Right, I’m gonna attack now to see if I can take the lead’ and I grained my tyres the front right tyre()” “Every lap was just so painful. I was going slower and slower I was like ‘oh this is not fun’, so yeah P3 was the maximum today()”
1:26

George 🗣️ “I had the steering problem again, from about lap 5 same as I had in quali, but I managed to drive around this and got used to the challenges of this problem. The pace looked quite good in stint 1 and then at the start of my 2 stint when Max came out of the pits I was like ‘Right, I’m gonna attack now to see if I can take the lead’ and I grained my tyres the front right tyre()” “Every lap was just so painful. I was going slower and slower I was like ‘oh this is not fun’, so yeah P3 was the maximum today()”

Mercedes-AMG Passion Club

192,727 views • 7 months ago

Linus Torvalds says that C is king for OS development due to its efficient hardware interaction and the ability to predict the assembly language output of C code.
1:18

Linus Torvalds says that C is king for OS development due to its efficient hardware interaction and the ability to predict the assembly language output of C code.

tetsuo

3,010,229 views • 1 year ago

I caught up with National Treasury CS, John Mbadi, to discuss the US$1.5 billion UAE linked credit line. Two questions from me: · When Kenya decided to go this route, IMF expressed misgivings about it. Now that we are at the Spring Meetings, has that divergence between GOK & the Fund been resolved? · We've been under the impression that whereas the facility is available, GOK has deliberately steered clear of drawing down from it. Why? Especially given the external funding pressures The CS says: · GOK will be drawing down US$500.0M from the UAE credit line as soon as next week. So GOK will be drawing down 1/3rd of the loan · The US$1.0 billion remaining will be kicked in 2025/26 commercial borrowing · Delay in the draw down was because GOK had been scouting for cheaper multilateral funding · GOK is now tapping the UAE credit line because of the headwinds on the multilateral funding side (i.e, the aborted 9th Review of the IMF programme, delay in the US$750.0M World Bank DPO VII & delay in the US$200.0M AfDB funding) · AfDB's US$200.0M should be hitting the coffers as soon as next week he says
2:48

I caught up with National Treasury CS, John Mbadi, to discuss the US$1.5 billion UAE linked credit line. Two questions from me: · When Kenya decided to go this route, IMF expressed misgivings about it. Now that we are at the Spring Meetings, has that divergence between GOK & the Fund been resolved? · We've been under the impression that whereas the facility is available, GOK has deliberately steered clear of drawing down from it. Why? Especially given the external funding pressures The CS says: · GOK will be drawing down US$500.0M from the UAE credit line as soon as next week. So GOK will be drawing down 1/3rd of the loan · The US$1.0 billion remaining will be kicked in 2025/26 commercial borrowing · Delay in the draw down was because GOK had been scouting for cheaper multilateral funding · GOK is now tapping the UAE credit line because of the headwinds on the multilateral funding side (i.e, the aborted 9th Review of the IMF programme, delay in the US$750.0M World Bank DPO VII & delay in the US$200.0M AfDB funding) · AfDB's US$200.0M should be hitting the coffers as soon as next week he says

Julians Amboko

31,673 views • 1 year ago