FabSwingers.com > Forums > The Lounge > Software developers
Software developers
Jump to: Newest in thread
| |||
Python here | |||
" I myself am a C# developer" Groan. If you really want to swear just shout "JScript" out loud. I did some C++ development back in the day but mostly work with LAMP stacks now. | |||
 | |||
 | |||
 | |||
"What? No Fortran or a bit of COBOL? "This is where my "programming" journey ended too... along with a bit of D-Base 
As tech support in a school I occasionally have to do a bit of VBA for Excel stuff, but try to avoid it if I can.
Cal | |||
 | |||
| |||
"Amos here
"Have dabbled with Amos, would have loved to chat but can’t dm you | |||
| |||
| |||
| |||
| |||
"How time flies, it is 45 years since I learned BASIC: 10 print “Fancy a fuck?” 20 goto 10 "ldx #$0 _loop lda $txt,x beq $end jsr $FFD2 inx bne $loop _end rts .txt "Fancy a fuck" .byte #$0 Bonus points for anyone who knows which computer this would be written for
EDIT: initially wrote a syntax error  | |||
"How time flies, it is 45 years since I learned BASIC: 10 print “Fancy a fuck?” 20 goto 10
ldx #$0
_loop
lda $txt,x
beq $end
jsr $FFD2
inx
bne $loop
_end
rts
.txt "Fancy a fuck"
.byte #$0
Bonus points for anyone who knows which computer this would be written for
EDIT: initially wrote a syntax error "Is it for a 6502 chipset based computer? | |||
"How time flies, it is 45 years since I learned BASIC: 10 print “Fancy a fuck?” 20 goto 10
ldx #$0
_loop
lda $txt,x
beq $end
jsr $FFD2
inx
bne $loop
_end
rts
.txt "Fancy a fuck"
.byte #$0
Bonus points for anyone who knows which computer this would be written for
EDIT: initially wrote a syntax error "Commodore 64? | |||
 but can you fix mine | |||
"How time flies, it is 45 years since I learned BASIC: 10 print “Fancy a fuck?” 20 goto 10
ldx #$0
_loop
lda $txt,x
beq $end
jsr $FFD2
inx
bne $loop
_end
rts
.txt "Fancy a fuck"
.byte #$0
Bonus points for anyone who knows which computer this would be written for
EDIT: initially wrote a syntax error
Commodore 64?"Yes 
How did you work it out? | |||
"How time flies, it is 45 years since I learned BASIC: 10 print “Fancy a fuck?” 20 goto 10
ldx #$0
_loop
lda $txt,x
beq $end
jsr $FFD2
inx
bne $loop
_end
rts
.txt "Fancy a fuck"
.byte #$0
Bonus points for anyone who knows which computer this would be written for
EDIT: initially wrote a syntax error
Commodore 64?
Yes
How did you work it out?"I am old enough to have had one. | |||
"Is it for a 6502 chipset based computer?" Yes
Wellhungvwe got it spot on, it was a Commodore 64
The clue being "jmp $ffd2"
Ffd2 is the memory address of a C64-specific kernal routine to print a character to the screen | |||
| |||
"How time flies, it is 45 years since I learned BASIC: 10 print “Fancy a fuck?” 20 goto 10
ldx #$0
_loop
lda $txt,x
beq $end
jsr $FFD2
inx
bne $loop
_end
rts
.txt "Fancy a fuck"
.byte #$0
Bonus points for anyone who knows which computer this would be written for
EDIT: initially wrote a syntax error
Commodore 64?
Yes
How did you work it out?
I am old enough to have had one."Unfortunately so am i
It was my first ever computer I got at age 6.
Despite technically being a computer that you could in theory use exactly as if it was a workstation, it was in fact just a glorified games console with a keyboard attached to it | |||
| |||
" It was my first ever computer I got at age 6. Despite technically being a computer that you could in theory use exactly as if it was a workstation, it was in fact just a glorified games console with a keyboard attached to it "Mine was actually an Apple2 - for various reasons I also had a modem and network access which was pretty cool as a kid in the late 70s! | |||
" It was my first ever computer I got at age 6. Despite technically being a computer that you could in theory use exactly as if it was a workstation, it was in fact just a glorified games console with a keyboard attached to it
Mine was actually an Apple2 - for various reasons I also had a modem and network access which was pretty cool as a kid in the late 70s!"That really would have been cool at that time using the internet is something I never got to experience on the c64 (although maybe in retrospect i wouldn't have wanted to ), and my dad wouldn't even get a disk drive, let alone a modem. | |||
" It was my first ever computer I got at age 6. Despite technically being a computer that you could in theory use exactly as if it was a workstation, it was in fact just a glorified games console with a keyboard attached to it
Mine was actually an Apple2 - for various reasons I also had a modem and network access which was pretty cool as a kid in the late 70s!
That really would have been cool at that time using the internet is something I never got to experience on the c64 (although maybe in retrospect i wouldn't have wanted to ), and my dad wouldn't even get a disk drive, let alone a modem. "It wasn’t the internet like we understand it today - it was point to point bulletin boards and a few other things. Basically it was the forums 45 years ago | |||
| |||
| |||
| |||
"How time flies, it is 45 years since I learned BASIC: 10 print “Fancy a fuck?” 20 goto 10 "30 RUN | |||
| |||
"I did know COBOL back in the day. Now it's mainly SQL, VBA and excel formulae and beginning to learn Power BI. " It isn't only computer memory that fades with time, I forgot to add VBA, SQL, Access and Excel. Outlook had some nifty form features too | |||
" It was my first ever computer I got at age 6. Despite technically being a computer that you could in theory use exactly as if it was a workstation, it was in fact just a glorified games console with a keyboard attached to it
Mine was actually an Apple2 - for various reasons I also had a modem and network access which was pretty cool as a kid in the late 70s!
That really would have been cool at that time using the internet is something I never got to experience on the c64 (although maybe in retrospect i wouldn't have wanted to ), and my dad wouldn't even get a disk drive, let alone a modem.
It wasn’t the internet like we understand it today - it was point to point bulletin boards and a few other things. Basically it was the forums 45 years ago "And probably took the best part of a minute to load a new message | |||
| |||
"i have no idea what on earth your talking about but can you fix mine"Easy Switch it off and on again | |||
| |||
| |||
"What? No Fortran or a bit of COBOL? "Company I cut my teeth with was COBOL and openroad. | |||
If anyone wants to collab on any projects give us a shout!
- J
Xx | |||
"SQL geek here Always happy to inner join my table with yours "V here (Mrs) I used to do a bit of SQL, J taught me and I do miss it. Unfortunately my current business doesn't really use it lol but hoping to implement it, miss the organisation of it hahaha. Love the innuendo lol. | |||
"Awesome that there are so many fellow developers
If anyone wants to collab on any projects give us a shout!
- J
Xx"I think that would be interesting but probably a bad idea
I’m curious though on you’re ‘stack’ amd maybe you can help . I recently inherited an offshore Node, React, Mongo outfit with some python for ETL jobs.
Why do you use React wlth c# not Node. Do you think Node is bad for web applications ? | |||
"Awesome that there are so many fellow developers
If anyone wants to collab on any projects give us a shout!
- J
Xx
I think that would be interesting but probably a bad idea
I’m curious though on you’re ‘stack’ amd maybe you can help . I recently inherited an offshore Node, React, Mongo outfit with some python for ETL jobs.
Why do you use React wlth c# not Node. Do you think Node is bad for web applications ? "So React is the front end framework to build components and display them visually (html with js essentialy) whereas Node is a Java script framework for the backend. It's not a comparison You could replace C# with Node etc
- J | |||
"Awesome that there are so many fellow developers
If anyone wants to collab on any projects give us a shout!
- J
Xx
I think that would be interesting but probably a bad idea
I’m curious though on you’re ‘stack’ amd maybe you can help . I recently inherited an offshore Node, React, Mongo outfit with some python for ETL jobs.
Why do you use React wlth c# not Node. Do you think Node is bad for web applications ?
So React is the front end framework to build components and display them visually (html with js essentialy) whereas Node is a Java script framework for the backend. It's not a comparison You could replace C# with Node etc
- J"I know I was curious why you choose c# on the back when you use react on the front - why not you use the same language front and back - node and react ? | |||
| |||
"SQL geek here Always happy to inner join my table with yours
V here (Mrs) I used to do a bit of SQL, J taught me and I do miss it. Unfortunately my current business doesn't really use it lol but hoping to implement it, miss the organisation of it hahaha.
Love the innuendo lol. "Why thank you | |||
"For anyone still coding now, what's everyone's code editor if choice? I've switched over to Notepad++ a few years ago just because it's easier to make custom syntax highlighting. It's also very lightweight. I used to use Sublime Text but I found trying to make custom highlighters in it frustrating & confusing. I effectively have to learn regex to do anything useful when it comes to syntax highlighting.. Visual Studio code is very bloaty & slow on my laptop, but I do like how many extensions it has & how easy it is to install extensions, unlike the latter 2 especially Sublime. I only really use it to look at binary files and VScode has a nice hex viewer." It depends on what I'm doing. For java I use intellij - before that I used eclipse. The typescript editor is home grown by the company I work for. It handles the UI layout too. Fortunately I have a decent work computer | |||
"Just wondered how many fellow coders/architects there are amongst us? Similar positions too? I myself am a C# developer, predominantly backend but using React as well. Both AWS and azure. Looking forward to hearing from fellow IT geeks! " Learned Fortran and Algol at college then went over electronics. Later decided to do hardware support. Then moved to web development in Asp.net VB , now only develop back end and API in c# and SQL server, power bi and ms automate | |||
"For anyone still coding now, what's everyone's code editor if choice? I've switched over to Notepad++ a few years ago just because it's easier to make custom syntax highlighting. It's also very lightweight. I used to use Sublime Text but I found trying to make custom highlighters in it frustrating & confusing. I effectively have to learn regex to do anything useful when it comes to syntax highlighting.. Visual Studio code is very bloaty & slow on my laptop, but I do like how many extensions it has & how easy it is to install extensions, unlike the latter 2 especially Sublime. I only really use it to look at binary files and VScode has a nice hex viewer. It depends on what I'm doing. For java I use intellij - before that I used eclipse. The typescript editor is home grown by the company I work for. It handles the UI layout too. Fortunately I have a decent work computer "Eclipse I remember that.
The last time I used it was probably around 2008 or 2009 while I was doing a Java college course. I remember it being a huge download (for the time) & it running really slowly on my admittedly crappy computer at the time.
I'm not familiar with Intellij, but I am very familiar with Android Studio which I believe is based on Intellij.
Android Studio has a similar problem, where if you're not careful, it downloads about 20 gigs worth of crap you don't need.
All I want is just the latest Android API and build tools, but then it gives me all this crap for Google Wear, Android TV etc. I'm just trying to build apps for phones & tablets.
I used to use the SDK Manager for installing libs which worked well enough, but now Android developers are being encouraged (forced) to use this behemoth IDE.
I've always tended to use PCs/laptops which are a generation or 2 behind contemporary hardware (to save money ), so file size & performance are always considerations for me unfortunately. | |||
| |||
"My hubby was a computer games designer in the 80s. Designed games on the Sinclair Spectrum mostly, quite well known at the time. His games featured on covers of Crash, Sinclair User, Your Sinclair amongst others. Mrs x" Awesome
For me mainly C#.NET and TSQL but using Python more and really need to pick up .NET Core | |||
| |||
they all wanted me to move from journalism and comms to programming but no way in hell. That stuff is difficult!
One of my boyfriends ran a MUD in Linux. Sometimes he got me spotting bugs in the code and my attention span was gone in 10 seconds.
What is Fab written in? HTML? | |||
| |||
" What is Fab written in? HTML? " Well, technically yes, just not exclusively | |||
"… Can't imagine how much things have changed for those in the thread who've been at it 30+! " The first computer I used was ‘programmed’ using paper cards, which you put into a grid holder and pressed out precut squares using a metal probe. You then fed the punched cards into a reader.  | |||
| |||
"… Can't imagine how much things have changed for those in the thread who've been at it 30+! The first computer I used was ‘programmed’ using paper cards, which you put into a grid holder and pressed out precut squares using a metal probe. You then fed the punched cards into a reader. "I would not have made it as Programmer in those days! | |||
"… Can't imagine how much things have changed for those in the thread who've been at it 30+! The first computer I used was ‘programmed’ using paper cards, which you put into a grid holder and pressed out precut squares using a metal probe. You then fed the punched cards into a reader. "I've heard some harrowing tales about the punchcard programming days, like how a large program could span over several dozen cards, and if for example you dropped the pile of cards on the floor, or did something else to cause the program to be out of order, it could take weeks to put it back in order again. And how if you made an error in your program, trying to go back & correct it would be a nightmare because you would need to manually trace back though the pile of cards to find where the error was, and then punch replacement cards with the fixed code
Punchcards are way before my time thankfully | |||
| |||
"What is Fab written in? HTML? " The tears of unicorns and the hopes of the masses. | |||
"
Python here"You snake !! ... | |||
| |||
| |||
| |||
and Haskell, wouldn’t wish that on my worst enemy haha l | |||
"… Can't imagine how much things have changed for those in the thread who've been at it 30+! The first computer I used was ‘programmed’ using paper cards, which you put into a grid holder and pressed out precut squares using a metal probe. You then fed the punched cards into a reader. "No way! When they mentioned this in the lectures and they asked if anyone would still be here if that was still the way today, had about 10/200 hands up haha | |||
| |||
"… Can't imagine how much things have changed for those in the thread who've been at it 30+! The first computer I used was ‘programmed’ using paper cards, which you put into a grid holder and pressed out precut squares using a metal probe. You then fed the punched cards into a reader.
I've heard some harrowing tales about the punchcard programming days, like how a large program could span over several dozen cards, and if for example you dropped the pile of cards on the floor, or did something else to cause the program to be out of order, it could take weeks to put it back in order again. And how if you made an error in your program, trying to go back & correct it would be a nightmare because you would need to manually trace back though the pile of cards to find where the error was, and then
punch replacement cards with the fixed code
Punchcards are way before my time thankfully "There were ways around the problem. Each card represented an 80 character line of code. There was space at the end of the card to add a sequence number (like a line number) so if you dropped the cards you could put them back in order. The top edge of the card had space to print the characters punched out below so you could check against a printed listing. We did all our first year programming exercises on cards when I was at uni. | |||
| |||
"… Can't imagine how much things have changed for those in the thread who've been at it 30+! The first computer I used was ‘programmed’ using paper cards, which you put into a grid holder and pressed out precut squares using a metal probe. You then fed the punched cards into a reader.
I've heard some harrowing tales about the punchcard programming days, like how a large program could span over several dozen cards, and if for example you dropped the pile of cards on the floor, or did something else to cause the program to be out of order, it could take weeks to put it back in order again. And how if you made an error in your program, trying to go back & correct it would be a nightmare because you would need to manually trace back though the pile of cards to find where the error was, and then
punch replacement cards with the fixed code
Punchcards are way before my time thankfully
There were ways around the problem. Each card represented an 80 character line of code. There was space at the end of the card to add a sequence number (like a line number) so if you dropped the cards you could put them back in order. The top edge of the card had space to print the characters punched out below so you could check against a printed listing.
We did all our first year programming exercises on cards when I was at uni."Even easier than that was to mark a thick diagonal line on the edge of the stacked cards. With so many Devs here, it's hard to understand why we put up with the technical wizardry that's Fabs. Am I the only one who thinks it looks like a website from the late 90s? Or maybe that's part of the chintzy charm.
I got gifted a punch tape reader/writer. Not sure what to do with it now, so the 8kg box is sat in the loft. | |||
| |||
"… Can't imagine how much things have changed for those in the thread who've been at it 30+! The first computer I used was ‘programmed’ using paper cards, which you put into a grid holder and pressed out precut squares using a metal probe. You then fed the punched cards into a reader.
I've heard some harrowing tales about the punchcard programming days, like how a large program could span over several dozen cards, and if for example you dropped the pile of cards on the floor, or did something else to cause the program to be out of order, it could take weeks to put it back in order again. And how if you made an error in your program, trying to go back & correct it would be a nightmare because you would need to manually trace back though the pile of cards to find where the error was, and then
punch replacement cards with the fixed code
Punchcards are way before my time thankfully
There were ways around the problem. Each card represented an 80 character line of code. There was space at the end of the card to add a sequence number (like a line number) so if you dropped the cards you could put them back in order. The top edge of the card had space to print the characters punched out below so you could check against a printed listing.
We did all our first year programming exercises on cards when I was at uni.
Even easier than that was to mark a thick diagonal line on the edge of the stacked cards.
With so many Devs here, it's hard to understand why we put up with the technical wizardry that's Fabs. Am I the only one who thinks it looks like a website from the late 90s? Or maybe that's part of the chintzy charm.
I got gifted a punch tape reader/writer. Not sure what to do with it now, so the 8kg box is sat in the loft."I still have a program on punched tape. It was the only way to move things between the computers we had at my first job after university. I turned it into a coaster. | |||
| |||
| |||
| |||
"… Can't imagine how much things have changed for those in the thread who've been at it 30+! The first computer I used was ‘programmed’ using paper cards, which you put into a grid holder and pressed out precut squares using a metal probe. You then fed the punched cards into a reader.
I've heard some harrowing tales about the punchcard programming days, like how a large program could span over several dozen cards, and if for example you dropped the pile of cards on the floor, or did something else to cause the program to be out of order, it could take weeks to put it back in order again. And how if you made an error in your program, trying to go back & correct it would be a nightmare because you would need to manually trace back though the pile of cards to find where the error was, and then
punch replacement cards with the fixed code
Punchcards are way before my time thankfully
There were ways around the problem. Each card represented an 80 character line of code. There was space at the end of the card to add a sequence number (like a line number) so if you dropped the cards you could put them back in order. The top edge of the card had space to print the characters punched out below so you could check against a printed listing.
We did all our first year programming exercises on cards when I was at uni.
Even easier than that was to mark a thick diagonal line on the edge of the stacked cards.
With so many Devs here, it's hard to understand why we put up with the technical wizardry that's Fabs. Am I the only one who thinks it looks like a website from the late 90s? Or maybe that's part of the chintzy charm.
I got gifted a punch tape reader/writer. Not sure what to do with it now, so the 8kg box is sat in the loft.
I still have a program on punched tape. It was the only way to move things between the computers we had at my first job after university.
I turned it into a coaster."What's the code on the coaster do? Print "Hello Java Beans?" | |||
"
Python here"Legend | |||
| |||
"… Can't imagine how much things have changed for those in the thread who've been at it 30+! The first computer I used was ‘programmed’ using paper cards, which you put into a grid holder and pressed out precut squares using a metal probe. You then fed the punched cards into a reader.
I've heard some harrowing tales about the punchcard programming days, like how a large program could span over several dozen cards, and if for example you dropped the pile of cards on the floor, or did something else to cause the program to be out of order, it could take weeks to put it back in order again. And how if you made an error in your program, trying to go back & correct it would be a nightmare because you would need to manually trace back though the pile of cards to find where the error was, and then
punch replacement cards with the fixed code
Punchcards are way before my time thankfully
There were ways around the problem. Each card represented an 80 character line of code. There was space at the end of the card to add a sequence number (like a line number) so if you dropped the cards you could put them back in order. The top edge of the card had space to print the characters punched out below so you could check against a printed listing.
We did all our first year programming exercises on cards when I was at uni.
Even easier than that was to mark a thick diagonal line on the edge of the stacked cards.
With so many Devs here, it's hard to understand why we put up with the technical wizardry that's Fabs. Am I the only one who thinks it looks like a website from the late 90s? Or maybe that's part of the chintzy charm.
I got gifted a punch tape reader/writer. Not sure what to do with it now, so the 8kg box is sat in the loft.
I still have a program on punched tape. It was the only way to move things between the computers we had at my first job after university.
I turned it into a coaster.
What's the code on the coaster do? Print "Hello Java Beans?" "No, it was/is a lens system design tool. Written in Fortran and could show the surfaces/ray paths on a Tektronix monitor. | |||
| |||
| |||
| |||
"Full stack here - C#, with some react for front end and a hell of a lot of yml stuff for the pipelines and git config " As I'm not a web dev, I always get slightly confused by the modern use of the term "stack". Whenever I think of a stack, I'm thinking of an area of memory where the program counter gets pushed onto when you jump to a sub-routine, and popped back when you return from the sub-routine | |||
| |||
"Full stack here - C#, with some react for front end and a hell of a lot of yml stuff for the pipelines and git config As I'm not a web dev, I always get slightly confused by the modern use of the term "stack". Whenever I think of a stack, I'm thinking of an area of memory where the program counter gets pushed onto when you jump to a sub-routine, and popped back when you return from the sub-routine " I’m not a fan of it too, I always think it’s just something management say to make the dev cycle sound fancy to clients. Are you referring to stuff you do on a green screen there  | |||
| |||
| |||
| |||
"Hey solutions architect here, vb.net,asp.net,sql,query m, c#, python, c, crystal (god love it) " Amazing - I'm guessing you've worked your way up from being a dev? Do you find it hard to find time to write code anymore? I aspire to become a solutions architect in ~10 or years time. Currently a senior dev, pushing tech lead so a lot of learning to do yet! | |||
"Hey solutions architect here, vb.net,asp.net,sql,query m, c#, python, c, crystal (god love it) Amazing - I'm guessing you've worked your way up from being a dev? Do you find it hard to find time to write code anymore? I aspire to become a solutions architect in ~10 or years time. Currently a senior dev, pushing tech lead so a lot of learning to do yet! " The best architects I have seen really understand the business. The technology is second to them. My advice to all senior devs is that the technology skills are only part of the things you need as you go up and, weirdly, they become less important to the other stuff - business understanding and social skills. | |||
| |||
| |||
| |||
| |||
| |||
"Does anyone know what cubase is written in? " Wow, that takes me back. Since it was on the Atari ST it was probably C and/or Assembly. But if it survives to this day then I would imagine it's a Frankenstein of parts by now. Might not even be any of the original code in there | |||
"Does anyone know what cubase is written in? Wow, that takes me back. Since it was on the Atari ST it was probably C and/or Assembly. But if it survives to this day then I would imagine it's a Frankenstein of parts by now. Might not even be any of the original code in there "Yes every few years it has a new version released. The last few years it's had video editing functionality also...so you can synchronise your music compositions to visuals if you're composing music for a film, or TV show etc. | |||
"Hey solutions architect here, vb.net,asp.net,sql,query m, c#, python, c, crystal (god love it) Amazing - I'm guessing you've worked your way up from being a dev? Do you find it hard to find time to write code anymore? I aspire to become a solutions architect in ~10 or years time. Currently a senior dev, pushing tech lead so a lot of learning to do yet! The best architects I have seen really understand the business. The technology is second to them. My advice to all senior devs is that the technology skills are only part of the things you need as you go up and, weirdly, they become less important to the other stuff - business understanding and social skills." A million percent this. The early part of your career is usually spent solving new problems (they'll all be new problems for a while), and learning new tools, technologies, and methodologies. After a while though you realise that there's so much in common between different problems, different companies, and different technologies. What matters is how you apply the right solutions to the problem at hand, and how you communicate with the business to deliver the right thing first time. Writing the code these days is often the boring bit, unless you hit some weird issue that drives up up the wall (which incidentally I think happens every bit as much these days if not more because of all the 'magic' provided by these frameworks in an effort to make us more efficient). | |||
| |||
| |||
Graphic USB, LWIP, RTOS, FOC.
Recent stuff was EV based, (nope I aint buying one)
| |||
| |||
been doing it 3 years after being here redundant in my previous career during Covid.
While in lockdown I started reading myself through YouTube and now have a full time contract with a large company and pretty happy | |||
| |||
