The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
Please vote in the Forum Structure Poll. Polling will close at 2PM EST on January 21, 2025.
Well, regardless of how we all choose to interpret it, it seems like they are taking action to try to fix the problem. A bit too late, perhaps, but organizations can really sit on some awful situations indefinitely until someone makes a big public stink.
I have a client at work. Let's call them Unnamed Government Contractor. Due to contractual demands and general asshattery from UGC, something that would take 1 line of code and 5 minutes is instead going to take upwards of 20 hours to complete. They require use of a specific program that is completely unnecessary and superfluous to the functioning of the system.
Basically, instead of calling 1 line of server-side code I have to get another IDE to do the exact same thing, just in a very convoluted way. I get to spend half a week working on this instead of doing useful things.
We can't say no to them either, because they have a fuckton of money and they pay us well. I am so angry right now!
Question: What's the protocol for adding libraries to a project? What I mean is do I include the library inside of the project?
So the project will have a folder called ProjectName. Inside that I have .settings folder, src, and other stuff... Should I include a lib folder in that as well? I don't like how this project is setup in SVN, where they commit the .project and .settings files (this is bad, I know) and I have to go through and find these libraries that are located on their computers in various places. I think we should have them in a lib folder within the project.
Question: What's the protocol for adding libraries to a project? What I mean is do I include the library inside of the project?
So the project will have a folder called ProjectName. Inside that I have .settings folder, src, and other stuff... Should I include a lib folder in that as well? I don't like how this project is setup in SVN, where they commit the .project and .settings files (this is bad, I know) and I have to go through and find these libraries that are located on their computers in various places. I think we should have them in a lib folder within the project.
All binary data should be excluded from a revision system.
Your system should be designed to compile from a pull with the minimal of fuss. So having a well documented setup plan is a must. Where to put your libraries, what versions, etc.
That's my stance, anyways.
Though I could make an exception that does have a lib folder, sure, so long as it wasn't bloated and didn't change much.
+1
admanbunionize your workplaceSeattle, WARegistered Userregular
I like that the way the timing of those posts worked out it looks like bowen is super confused by the concept of libraries.
Question: What's the protocol for adding libraries to a project? What I mean is do I include the library inside of the project?
So the project will have a folder called ProjectName. Inside that I have .settings folder, src, and other stuff... Should I include a lib folder in that as well? I don't like how this project is setup in SVN, where they commit the .project and .settings files (this is bad, I know) and I have to go through and find these libraries that are located on their computers in various places. I think we should have them in a lib folder within the project.
All binary data should be excluded from a revision system.
Your system should be designed to compile from a pull with the minimal of fuss. So having a well documented setup plan is a must. Where to put your libraries, what versions, etc.
That's my stance, anyways.
Though I could make an exception that does have a lib folder, sure, so long as it wasn't bloated and didn't change much.
I agree. Most of the guys here commit their .project files and .settings stuff. It makes it very annoying to pull the project down, but generally there is only a single person per project. So I can sorta see why they did it.
This project only requires two libraries it seems. Not big ones (log4j stuff).
Question: What's the protocol for adding libraries to a project? What I mean is do I include the library inside of the project?
So the project will have a folder called ProjectName. Inside that I have .settings folder, src, and other stuff... Should I include a lib folder in that as well? I don't like how this project is setup in SVN, where they commit the .project and .settings files (this is bad, I know) and I have to go through and find these libraries that are located on their computers in various places. I think we should have them in a lib folder within the project.
All binary data should be excluded from a revision system.
Your system should be designed to compile from a pull with the minimal of fuss. So having a well documented setup plan is a must. Where to put your libraries, what versions, etc.
That's my stance, anyways.
Though I could make an exception that does have a lib folder, sure, so long as it wasn't bloated and didn't change much.
Right, super common thing, which is why there are all sorts of helpers and tools that pull and manage external dependencies.
The Right Way is to not include externals in your source control, but instead to have a file that documents the dependencies. Either a text document that just lists what is needed (with version numbers you used) and where to put them manually, or a manifest for a tool that pulls those dependencies for your and includes them automatically during a build.
The exact tool depends on what you're developing with, but the idea is the same always: don't include externals.
I can't even fathom a situation where you'd encounter an issue like that.
Like... can you give example code?
There is a complex business process where emails need to be sent at specific times, like when tasks are approved and stuff.
Instead of calling the SPUtility.SendEmail function, the company is requiring us to use a workflow in a separate IDE. Which will essentially call the SPUtility.SendEmail function, just not from C#, it will do it from this specialized program they are requiring us to use for emails. There is no reason to do this, not even for security purposes. It's all going to come from the same place whether it's done from C# or not.
Huh. I really expected Scheme and Lisp type languages to be harder.
Recursion, bitches!
Smug LISP weenies who write tutorials and manuals spend so much time condensingly telling your that you mind is going to be blown rather than just explaining the fucking language that they build up a massive fog of pseudo-imenetrabilty about LISP and Scheme.
No you smug fucks, I am perfectly happy with the concept of first class functions, you don't need to spend a chapter preparing me for the concept.
admanbunionize your workplaceSeattle, WARegistered Userregular
To be fair, when most Scheme and LISP guides were written the concepts they were explaining had not made their way into the core of the majority of mainstream programming languages.
To be fair, when most Scheme and LISP guides were written the concepts they were explaining had not made their way into the core of the majority of mainstream programming languages.
I am never fair to smug LISP weenies. C has function pointers as a common work-a-day part of the language. The idea of passing a function as an argument is not some kind of esoteric forbidden knowledge.
Pretty much the only person who'd going to have their mind "blown" by LISP concepts is a Java 1.2 code monkey. FORTH has a REPL too you cocks.
To be fair, when most Scheme and LISP guides were written the concepts they were explaining had not made their way into the core of the majority of mainstream programming languages.
I am never fair to smug LISP weenies. C has function pointers as a common work-a-day part of the language. The idea of passing a function as an argument is not some kind of esoteric forbidden knowledge.
Pretty much the only person who'd going to have their mind "blown" by LISP concepts is a Java 1.2 code monkey. FORTH has a REPL too you cocks.
Function pointers aren't the mind-blowing part of scheme. First-class function values and closures, immutability-by-default, and recursion-as-norm-rather-than-exception, are the bits that are foreign to most working programmers.
@TwitchTV, @Youtube: master-level zerg ladder/customs, commentary, and random miscellany.
0
gavindelThe reason all your softwareis brokenRegistered Userregular
Fully* functional file system built and turned in. Took roughly 45 hours of coding (including bug testing).
This project is due tomorrow night at midnight. Sitting outside class today, I asked other students how they had done it. Of the seven I asked, one had finished, five hadn't started, and one had a rather interesting solution: she made a linear file system. Delete something? too bad, those sectors are gone forever! Fill up a disk? Buy a new one!
I ended up giving a mini lecture on how you can use fseek, fread, and fwrite to set up a virtual system, and I think 20 people were listening in by the end. God help these sods unless they're way, way faster at this than me. Gonna be a lot of redbull tonight.
*As long as you don't check any error flags
*As long as you don't want more than 2048 sectors
*As long as don't mind your files coming out the other end padded to the nearest 256 by nulls
*You didn't want full pathing support, right?
To be fair, when most Scheme and LISP guides were written the concepts they were explaining had not made their way into the core of the majority of mainstream programming languages.
I am never fair to smug LISP weenies. C has function pointers as a common work-a-day part of the language. The idea of passing a function as an argument is not some kind of esoteric forbidden knowledge.
Pretty much the only person who'd going to have their mind "blown" by LISP concepts is a Java 1.2 code monkey. FORTH has a REPL too you cocks.
Most of the C guys who took the Artificial Intelligence classes with me in the mid-90s did not take kindly to LISP. But those guys weren't happy unless code was the absolutely most efficient/fastest it could be, and god forbid somebody was able to look at what was written and be able to understand it.
LISP was my... fourth? Fifth?... language, and I thought it was pretty cool. Landed a bunch of callbacks and two jobs because I put it on my resume and actually knew what I was talking about. Even programmed it professionally for a couple years.
Fully* functional file system built and turned in. Took roughly 45 hours of coding (including bug testing).
This project is due tomorrow night at midnight. Sitting outside class today, I asked other students how they had done it. Of the seven I asked, one had finished, five hadn't started, and one had a rather interesting solution: she made a linear file system. Delete something? too bad, those sectors are gone forever! Fill up a disk? Buy a new one!
I ended up giving a mini lecture on how you can use fseek, fread, and fwrite to set up a virtual system, and I think 20 people were listening in by the end. God help these sods unless they're way, way faster at this than me. Gonna be a lot of redbull tonight.
*As long as you don't check any error flags
*As long as you don't want more than 2048 sectors
*As long as don't mind your files coming out the other end padded to the nearest 256 by nulls
*You didn't want full pathing support, right?
I wonder how many will just write an app that loopback mounts an ext filesystem and just proxies the data?
Fully* functional file system built and turned in. Took roughly 45 hours of coding (including bug testing).
This project is due tomorrow night at midnight. Sitting outside class today, I asked other students how they had done it. Of the seven I asked, one had finished, five hadn't started, and one had a rather interesting solution: she made a linear file system. Delete something? too bad, those sectors are gone forever! Fill up a disk? Buy a new one!
I ended up giving a mini lecture on how you can use fseek, fread, and fwrite to set up a virtual system, and I think 20 people were listening in by the end. God help these sods unless they're way, way faster at this than me. Gonna be a lot of redbull tonight.
*As long as you don't check any error flags
*As long as you don't want more than 2048 sectors
*As long as don't mind your files coming out the other end padded to the nearest 256 by nulls
*You didn't want full pathing support, right?
Reminds me of my networking class. Our second big project was the usual "intro to network programming second project", which is to say, implement TCP on top of UDP.
A couple days out, I had kids asking me how I was doing it not too dissimilar from what you described.
Man, I rocked that class. I mean, I was pretty good at my systems classes too, but yeah that was the reason I ended up at my current company that's not about to be my current company in less than 72 hours.
To be fair, when most Scheme and LISP guides were written the concepts they were explaining had not made their way into the core of the majority of mainstream programming languages.
I am never fair to smug LISP weenies. C has function pointers as a common work-a-day part of the language. The idea of passing a function as an argument is not some kind of esoteric forbidden knowledge.
Pretty much the only person who'd going to have their mind "blown" by LISP concepts is a Java 1.2 code monkey. FORTH has a REPL too you cocks.
Function pointers aren't the mind-blowing part of scheme. First-class function values and closures, immutability-by-default, and recursion-as-norm-rather-than-exception, are the bits that are foreign to most working programmers.
I feel bad because I don't like recursion.
0
gavindelThe reason all your softwareis brokenRegistered Userregular
What my professors say when I use recursion: "Great! You really understand the concept!"
What the TA says: "Ugh, fine."
What the workplace says: "What the hell is this crap? Change it, half your coworkers can't read it."
It's not that we can't read it, it's just that I hate it. Same with regex. Though at this point I can't read regex anymore so I've got that going for me.
Really though, recursion should be "well there really is just not a better way to do this." (some of the more advanced data structure stuff like trees use it)
If you're using recursion for something like fibonacci you deserve to be strung up and stabbed.
And if you're using regex you're gonna have a bad time.
My new project has me working in Linux a lot more and I'm quite enjoying it. I only knew a handful of commands but now I'm starting to brush up on my command line experience.
We really don't need to use much recursion in our standard C# coding at work but holy crap being able to use recursive CTE's in MSSQL is the light. It makes certain queries in SQL so much easier. Being able to do all your standard recursion cases in the db like getting all child nodes, figuring out effective permissions/settings that are inherited from parent configurations is great.
So I'm looking at trying to build a knowledge base for programming (not language specific). I want to start with some math texts and Concrete Mathematics is mentioned in a number of searches I've done. Any other recommendations?
And as a follow on, any recommendations on good programming concept texts?
Is there no way to copy some text from a Terminal Session into a file in Nano? I have to encrypt a password using a UTIL we have and it outputs the result onto the screen and I need to copy/paste that into a properties file.
Posts
I guess it's something donglegate lady had commented on or something.
I have a client at work. Let's call them Unnamed Government Contractor. Due to contractual demands and general asshattery from UGC, something that would take 1 line of code and 5 minutes is instead going to take upwards of 20 hours to complete. They require use of a specific program that is completely unnecessary and superfluous to the functioning of the system.
Basically, instead of calling 1 line of server-side code I have to get another IDE to do the exact same thing, just in a very convoluted way. I get to spend half a week working on this instead of doing useful things.
We can't say no to them either, because they have a fuckton of money and they pay us well. I am so angry right now!
So the project will have a folder called ProjectName. Inside that I have .settings folder, src, and other stuff... Should I include a lib folder in that as well? I don't like how this project is setup in SVN, where they commit the .project and .settings files (this is bad, I know) and I have to go through and find these libraries that are located on their computers in various places. I think we should have them in a lib folder within the project.
Like... can you give example code?
All binary data should be excluded from a revision system.
Your system should be designed to compile from a pull with the minimal of fuss. So having a well documented setup plan is a must. Where to put your libraries, what versions, etc.
That's my stance, anyways.
Though I could make an exception that does have a lib folder, sure, so long as it wasn't bloated and didn't change much.
I agree. Most of the guys here commit their .project files and .settings stuff. It makes it very annoying to pull the project down, but generally there is only a single person per project. So I can sorta see why they did it.
This project only requires two libraries it seems. Not big ones (log4j stuff).
Right, super common thing, which is why there are all sorts of helpers and tools that pull and manage external dependencies.
The Right Way is to not include externals in your source control, but instead to have a file that documents the dependencies. Either a text document that just lists what is needed (with version numbers you used) and where to put them manually, or a manifest for a tool that pulls those dependencies for your and includes them automatically during a build.
The exact tool depends on what you're developing with, but the idea is the same always: don't include externals.
There is a complex business process where emails need to be sent at specific times, like when tasks are approved and stuff.
Instead of calling the SPUtility.SendEmail function, the company is requiring us to use a workflow in a separate IDE. Which will essentially call the SPUtility.SendEmail function, just not from C#, it will do it from this specialized program they are requiring us to use for emails. There is no reason to do this, not even for security purposes. It's all going to come from the same place whether it's done from C# or not.
Smug LISP weenies who write tutorials and manuals spend so much time condensingly telling your that you mind is going to be blown rather than just explaining the fucking language that they build up a massive fog of pseudo-imenetrabilty about LISP and Scheme.
No you smug fucks, I am perfectly happy with the concept of first class functions, you don't need to spend a chapter preparing me for the concept.
I made a game, it has penguins in it. It's pay what you like on Gumroad.
Currently Ebaying Nothing at all but I might do in the future.
I am never fair to smug LISP weenies. C has function pointers as a common work-a-day part of the language. The idea of passing a function as an argument is not some kind of esoteric forbidden knowledge.
Pretty much the only person who'd going to have their mind "blown" by LISP concepts is a Java 1.2 code monkey. FORTH has a REPL too you cocks.
I made a game, it has penguins in it. It's pay what you like on Gumroad.
Currently Ebaying Nothing at all but I might do in the future.
Function pointers aren't the mind-blowing part of scheme. First-class function values and closures, immutability-by-default, and recursion-as-norm-rather-than-exception, are the bits that are foreign to most working programmers.
This project is due tomorrow night at midnight. Sitting outside class today, I asked other students how they had done it. Of the seven I asked, one had finished, five hadn't started, and one had a rather interesting solution: she made a linear file system. Delete something? too bad, those sectors are gone forever! Fill up a disk? Buy a new one!
I ended up giving a mini lecture on how you can use fseek, fread, and fwrite to set up a virtual system, and I think 20 people were listening in by the end. God help these sods unless they're way, way faster at this than me. Gonna be a lot of redbull tonight.
*As long as you don't check any error flags
*As long as you don't want more than 2048 sectors
*As long as don't mind your files coming out the other end padded to the nearest 256 by nulls
*You didn't want full pathing support, right?
LISP was my... fourth? Fifth?... language, and I thought it was pretty cool. Landed a bunch of callbacks and two jobs because I put it on my resume and actually knew what I was talking about. Even programmed it professionally for a couple years.
I still have fond memories of CAR and CDR.
I wonder how many will just write an app that loopback mounts an ext filesystem and just proxies the data?
Now to figure out if this is Eloquent or MySQL being drunk.
edit: yes, column is nullable.
Reminds me of my networking class. Our second big project was the usual "intro to network programming second project", which is to say, implement TCP on top of UDP.
A couple days out, I had kids asking me how I was doing it not too dissimilar from what you described.
Man, I rocked that class. I mean, I was pretty good at my systems classes too, but yeah that was the reason I ended up at my current company that's not about to be my current company in less than 72 hours.
I feel bad because I don't like recursion.
What the TA says: "Ugh, fine."
What the workplace says: "What the hell is this crap? Change it, half your coworkers can't read it."
It's not that we can't read it, it's just that I hate it. Same with regex. Though at this point I can't read regex anymore so I've got that going for me.
Really though, recursion should be "well there really is just not a better way to do this." (some of the more advanced data structure stuff like trees use it)
If you're using recursion for something like fibonacci you deserve to be strung up and stabbed.
And if you're using regex you're gonna have a bad time.
But vim... Man... That's going to take a bit.
Nintendo ID: Incindium
PSN: IncindiumX
It's all terminal sessions. I don't ever actually see a GUI.
Nano then. Use space in your head to store minutia about your programming language, not your editor
http://www.math.umn.edu/systems_guide/putty_xwin32.html
NANO that's what I was trying to remember. I thought it was gedit... But that is a GUI program.
Yeah but I'm not sure if they'd be cool with me installing another program. We're already getting ripped for using up the HDD space on these machines.
Xming and putty are portable apps, so you don't need to install them.
They really going to give you grief over installing something under 2mb?
Just make sure it's in Java.
http://i.imgur.com/F1NXX.gif
And as a follow on, any recommendations on good programming concept texts?
It's the Government, so... Probably. :P
As long as the unix/terminal is modern enough anyways.
To copy from a terminal, just highlight the text with your mouse.
or if you're terminal only, I think you can insert text from a file in nano (or maybe it was pico...).
OR, cat some_file >> other_file (to append it to other_file), then you can move it around from within nano.